Include DRAGEN metrics in MULTIQC report

[RHReynolds]

Major changes include:

• Including .csv outputs from DRAGEN, which can be used as inputs for the MULTIQC module.
• Updates to modules: this was primarily motivated by inclusion of DRAGEN metrics in MULTIQC and avoidance of the following issue (MultiQC v1.13 can't read Dragen 4.0.3. mapping metrics file: TypeError: can't multiply sequence by non-int of type 'float' MultiQC/MultiQC#1765)
• Addition of stubrun in the dragen.nf module to test the logic of the workflow and to ensure DRAGEN metrics are captured by MULTIQC

Minor changes include:

• Addition of the arm profile for docker (testing on a mac, sorry!)
• Addition of ${meta.id}/ to the publishDir for the DRAGEN modules, so that DRAGEN outputs are stored in separate folders for each sample

PR checklist

• This comment contains a description of changes (with reason).
• Ensure the test suite passes (nextflow run . -profile test,docker).
• CHANGELOG.md is updated.

[drpatelh]

Looks awesome! Thanks @RHReynolds ! 😍

Maybe we can use -stub to run the tests given we can't really test DRAGEN via native Github Actions machines. Hopefully, that will give us something to test though for CI/CD.

[RHReynolds]

That sounds like a good idea. Do you know of a way to run -stub only for particular processes?

I ended up removing the stub part of the multiqc script (see multiqc.diff), just to check whether the stub part of the dragen script had worked, and prompted multiqc.

We could do the same for other nf-core modules, and just introduce a .diff patch, but thought I'd check if there's another/better way of doing it :)

Happy to implement whichever strategy in this PR, or a new PR, if that's more appropriate.