migrate fastp and fastplong to topics version channels

[eit-maxlcummins]

Updating fastp and fastplong modules to migrate versions to topic channels.

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

[mashehu]

@nf-core-bot fix linting

[SPPearce]

You need to also remove the mixing of the ch_versions from the subworkflows that use fastp (and regenerate the snapshots).

[SPPearce]

Need to update subworkflows

[eit-maxlcummins]

Need to update subworkflows

Does this mean I would have to update all other modules in all of the subworkflows that use fastp or fastplong as well to complete this PR?

[mashehu]

no, subworkflows should support the mixed usage of versions