new module: bedtools/nuc

[lmfaber]

PR checklist

Closes #6783

• 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 module conventions in the contribution docs
• If necessary, include test data in your PR.
• Remove all TODO statements.
• Emit the versions.yml file.
• Follow the naming conventions.
• Follow the parameters requirements.
• Follow the input/output options guidelines.
• Add a resource label
• Use BioConda and BioContainers if possible to fulfil software requirements.
• Ensure that the test works with either Docker / Singularity. Conda CI tests can be quite flaky:
  • For modules:
    • nf-core modules test <MODULE> --profile docker
    • nf-core modules test <MODULE> --profile singularity
    • nf-core modules test <MODULE> --profile conda
  • For subworkflows:
    • nf-core subworkflows test <SUBWORKFLOW> --profile docker
    • nf-core subworkflows test <SUBWORKFLOW> --profile singularity
    • nf-core subworkflows test <SUBWORKFLOW> --profile conda

[lmfaber]

I just saw that this PR includes commits from an earlier contribution I made (jvarkit/sam2tsv). The changes were merged in the meanwhile. Shall I submit a new PR without these commit messages or is this ok?

[edmundmiller]

I just saw that this PR includes commits from an earlier contribution I made (jvarkit/sam2tsv). The changes were merged in the meanwhile. Shall I submit a new PR without these commit messages or is this ok?

Shouldn't effect the squash really but if you want you can rebase off master and that should remove them!