Use branch-deploy action

[kevinbackhouse]

Use the Branch Deploy Action to determine who is allowed to trigger these workflows. pull_request_target is quite dangerous because it can be triggered by anyone, and it runs with write permissions to the repo, so it could enable an attacker to push new commits to the repo. Similarly, issue comments can be created by anybody. The Branch Deploy Action will only allow people with write permissions to trigger these workflows.

PR checklist

• This comment contains a description of changes (with reason)
• CHANGELOG.md is updated
• If you've fixed a bug or added code that should be tested, add tests!
• Documentation in docs is updated

[github-actions]

This PR is against the main branch ❌

• Do not close this PR
• Click Edit and change the base to dev
• This CI test will remain failed until you push a new commit

---

Hi @kevinbackhouse,

It looks like this pull-request is has been made against the kevinbackhouse/nf-core-tools main branch.
The main branch on nf-core repositories should always contain code from the latest release.
Because of this, PRs to main are only allowed if they come from the kevinbackhouse/nf-core-tools dev branch.

You do not need to close this PR, you can change the target branch to dev by clicking the "Edit" button at the top of this page.
Note that even after this, the test will continue to show as failing until you push a new commit.

Thanks again for your contribution!

[mashehu]

@nf-core-bot fix linting

[mirpedrol]

Thank you for the improvement @kevinbackhouse