Add finaletoolkit/endmotifs

[lbeltrame]

This is yet another subtool from Finale Toolkit. From the upstream documentation:

Measures frequency of k-mer 5’ end motifs.

It is required to land support for another tool which computes Motif Diversity Score (MDS).

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 module conventions in the contribution docs
• If necessary, include test data in your PR.
• Remove all TODO statements.
• Broadcast software version numbers to topic: versions - See version_topics
• 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

[SPPearce]

Can the tool cope with cram files?

[lbeltrame]

@SPPearce the newest version supports CRAM (not the one we have here), but if you don't mind I'll add first all the tools then make a sweeping follow-up PR to update versions and inputs in all the modules (I need one more PR for one last subcommand).

Would that be OK?

[SPPearce]

@SPPearce the newest version supports CRAM (not the one we have here), but if you don't mind I'll add first all the tools then make a sweeping follow-up PR to update versions and inputs in all the modules (I need one more PR for one last subcommand).

Would that be OK?

Sure, it was mostly just to detail that in the meta.yml