Added nf-core module presto/pairseq

[Vivian0105]

Open issue: #12206

PR checklist

Closes #XXX

• 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

[ggabernet]

Agreed with @mashehu comments, otherwise it looks good to me

[SPPearce]

Can you simplify this to one command (sed -n perhaps)? LLMs are very good at this.

[Vivian0105]

If use "sed", it will be:
tuple
val("${task.process}"),
val('presto'),
eval('PairSeq.py --version | sed -n "s/^PairSeq.py: \([0-9.]\)./\1/p"'),
emit: versions_presto,
topic: versions

For me, I feel it's harder to understand than grep + head.
Which one do you prefer?

Here's how PairSeq.py --version looks like (for your reference):
PairSeq.py: 0.7.9 2026.04.14