migrate lissero module to topic channels

[Anifowak]

PR checklist

Closes #11908

• 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

[Anifowak]

The remaining failure appears unrelated to the topic-channel migration. The lissero process fails with ModuleNotFoundError: No module named 'pkg_resources', likely due to missing setuptools in the environment.

Please advise whether you’d like me to add setuptools to the module environment or leave this outside the scope of the topic migration.

Thank you

[SPPearce]

Yes, we need to pin setuptools to make it work on conda. There are a bunch of other modules we've had to do this with.

[SPPearce]

Suggested change

	process.out.versions_lissero
	sanitizeOutput(process.out, unstableKeys: ["tsv"])