Remove vulnerable PR-comment artifact pattern

[mashehu]

Security patch

This PR applies a security fix included in nf-core/tools 4.0.3 for a potential exploit in the GitHub Actions workflows that post comments on pull requests.

For details, see the related security advisory: https://nf-co.re/advisories/pr-comment-workflow-vulnerability

The fix must be merged into the default branch to take effect. Please merge this PR as soon as possible.

These changes only affect CI workflows, so merging them into the default branch does not require a new pipeline release.

Note on how this patch was produced

This pipeline's TEMPLATE branch has not received the nf-core/tools 4.0.3 sync, so the change could not be generated from it. It was taken from nf-core/abotyper's TEMPLATE branch instead, with the repository identity in branch.yml rewritten for this pipeline — the only pipeline-specific content the template renders into any of these workflow files. Syncing the template separately is still worth doing, but does not block this fix.

[github-actions]

YAML linting is failing

To keep the code consistent with lots of contributors, we run automated code consistency checks.
To fix this CI test, please run:

• Install yaml-lint
  • Install npm then install yaml-lint (npm install -g yaml-lint)
• Fix the markdown errors
  • Run the test locally: yamllint $(find . -type f -name "*.yml" -o -name "*.yaml")
  • Fix any reported errors in your YAML files

Once you push these changes the test should pass, and you can hide this comment 👍

We highly recommend setting up yaml-lint in your code editor so that this formatting is done automatically on save. Ask about it on Slack for help!

Thanks again for your contribution!

[github-actions]

Markdown linting is failing

To keep the code consistent with lots of contributors, we run automated code consistency checks.
To fix this CI test, please run:

• Install markdownlint-cli
  • On Mac: brew install markdownlint-cli
  • Everything else: Install npm then install markdownlint-cli (npm install -g markdownlint-cli)
• Fix the markdown errors
  • Automatically: markdownlint . --config .github/markdownlint.yml --fix
  • Manually resolve anything left from markdownlint . --config .github/markdownlint.yml

Once you push these changes the test should pass, and you can hide this comment 👍

We highly recommend setting up markdownlint in your code editor so that this formatting is done automatically on save. Ask about it on Slack for help!

Thanks again for your contribution!