Sentieon DNAseq flow

[asp8200]

Questions

1. We have a test-config for sentieon-dedup, but not the other tests of sentieon; should we also have a test-config for, say, sentieon-haplotyper?
2. We have the tools-options haplotypecalller and sentieon_haplotyper but the skip_tools-options haplotypecalller_filter and haplotyper_filter. Should haplotyper_filter perhaps be renamed to sentieon_haplotyper_filter?

PR checklist

• This comment contains a description of changes (with reason).
• If you've fixed a bug or added code that should be tested, add tests!
• If you've added a new tool - have you followed the pipeline conventions in the contribution docs- [ ] If necessary, also make a PR on the nf-core/sarek branch on the nf-core/test-datasets repository.
• Make sure your code lints (nf-core lint).
• Ensure the test suite passes (nextflow run . -profile test,docker --outdir <OUTDIR>).
• Usage Documentation in docs/usage.md is updated.
• Output Documentation in docs/output.md is updated.
• CHANGELOG.md is updated.
• README.md is updated (including new tool citations and authors/contributors).

[github-actions]

Python linting (black) 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 black: pip install black
• Fix formatting errors in your pipeline: black .

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

We highly recommend setting up Black 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!

[maxulysse]

fixed the merge conflicts in nextflow.config due to merging the mutect2 PR

[asp8200]

@nf-core-bot fix linting