Test data uses paths instead of config map

[adamrtalbot]

Module test data uses paths rather than config map

Motivation:

• This makes modules and subworkflows completely portable, just depending on the parameter for the base path. You can install them in your pipeline code and have tests for everything!

We've been using it quite effectively for fetchngs and rnaseq. We were able to add test for all modules rnaseq with one module update!

Requires some more automation to make it simpler.

Will close #2858

PR checklist

• This comment contains a description of changes (with reason)
• CHANGELOG.md is updated
• If you've fixed a bug or added code that should be tested, add tests!
• Documentation in docs is updated

[mirpedrol]

The change to paths looks good to me for the modules repo 🙂 but we should also add the nf-test config file to the pipeline template, otherwise tests are not functional on pipelines.
I think it would be better to transition to nf-test completely, we have been adding nf-test changes slowly to the pipeline template and I think it's becoming confusing, and some of the functionality is currently broken. Do you think it would be good to make a big nf-test PR?

[adamrtalbot]

Yep I think so. Let's get it all done in one big release.