Add module `muse/call` and Dockerfile

[famosab]

PR checklist

Closes #5621

• [ ] This comment contains a description of changes (with reason).
• [x] If you've fixed a bug or added code that should be tested, add tests!
• [x] If you've added a new tool - have you followed the module conventions in the contribution docs
• [x] If necessary, include test data in your PR.
• [x] Remove all TODO statements.
• [x] Emit the versions.yml file.
• [ ] Follow the naming conventions.
• [ ] Follow the parameters requirements.
• [ ] Follow the input/output options guidelines.
• [x] Add a resource label
• [x] 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:
    • [x] 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

The Docker image still needs to be pushed to the nf-core registry, then I can update the paths accordingly. Also relates to #5629

[SPPearce]

Could this tool be added to BioConda? Then the other containers would be generated automatically

[famosab]

I opened a PR: https://github.com/bioconda/bioconda-recipes/pull/47957

If that works, I will change the files in this PR accordingly

[famosab]

I asked here: https://github.com/wwylab/MuSE/issues/31 Will wait for their reply and merge afterwards :)

[famosab]

@SPPearce I added the .bai files alongside the .bam building ontop of the answer I got from the developers. Do you think its ok like this?