UMICollapse module: Drop external dependencies from UMICollapse module tests

[MatthiasZepper]

Currently, the UMICollapse module tests run on data that is generated in the test setup{} with external dependencies (umitools/extract, bwa/index, bwa/mem, samtools/index). While this is no problem here in the modules' repository, those tests will fail on the pipeline level, if those additional modules are not available there.

While it may, on the long-term, be useful to devise a CI step detecting and installing missing modules for tests (Leon Rauschning made a neat proposal for this), I have now, due to time contraints, opted to add the required files to the test datasets (test-datasets/1390) and change the tests accordingly (this PR).

I have also updated the umi-tools dedup tests, since they so far used inputs without UMIs.

PR checklist

• This comment contains a description of changes (with reason).
• 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]

Looks much better.
Think you just need to swap to using the nft-bam plugin to test the bam files then should be good.