[New module] Infernal cmsearch

[prototaxites]

Adds a module for infernal's cmsearch tool. Pretty much a drop-in replacement for hmmsearch - I've basically cloned the module in its entirety.

[DONE] Once https://github.com/nf-core/test-datasets/pull/1542 is in I'll change the path to the model file in the tests.

PR checklist

Closes #XXX

• [x] This comment contains a description of changes (with reason).
• [ ] 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.
• [x] Follow the naming conventions.
• [x] Follow the parameters requirements.
• [x] 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

[prototaxites]

Thanks for the review!

Because the tool is by the same authors of (and has the same interface as) hmmer/hmmsearch, I copied the module code itself almost verbatim from https://github.com/nf-core/modules/blob/master/modules/nf-core/hmmer/hmmsearch/main.nf.

I would tend to agree about leaving the optional flags to the args, but left it as-is to keep the same interface as the other module. Happy to drop it though, but in which case, do you think the module still try and gzip optional outputs if they exist? In large cases I imagine they could become quite sizable.

[prototaxites]

OK, have looked into removing these val inputs - having taken some input on the #modules Slack (https://nfcore.slack.com/archives/CJRH30T6V/p1742982305507179) - I think in this case they're better to leave in, as there is a lot of ambiguity in the possible file names a user could specify in ext.args that wouldn't match the output block specifications, especially for the .tbl output which is a commented tabular format. This way we can enforce a schema on file extensions, which also makes the gzip compression element more stable too.