Update CONCOCT module(s): conda build bump, stub, and nf-test

[jfy133]

For the last three modules (same changes for all)

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.
• [ ] Emit the versions.yml file.
• [ ] 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

[jfy133]

@SPPearce Re the empty stub files, suprisingly this seems to be a silent fail. I have some channel manipulation during setup which I guess is failing for some reason, and causes no input to actually get to the module under testing... not sure why this works during the actual test and not the stup...

[SPPearce]

Does one of the upstream tools not have a stub? Or the stub doesn't produce the output file?

[jfy133]

Does one of the upstream tools not have a stub? Or the stub doesn't produce the output file?

All the tools have the stub. All I can think was the upstream stub was also broken... (in that it also produced no files...) I don't know.

REgardless changed in the input system and all works now, should be ready for re-review!