DSL2: New test config structure

[jfy133]

To try and balance comprehensiveness vs not too many parallel test jobs, @TCLamnidis and I mapped out a new test config structure.

This ensure all modules are touched at least once, and partially reflects a sort of typical run for different contexts. At the same time it ensures we don't have 100000s of test configs with all possible test combinations.

The plan is as follows

nf-core/eager v3.0.0 new test config structure

0. Test nothing
   • Everything off (for fast fail)
1. Test (default)
   • fastqc
   • (singleref) refIndex
   • adapterremoval
   • sharding
   • bwa aln
   • bam_filtering
   • markdup
   • preseq
   • damageprofiler
   • qualimap
   • MetaPhlAn
   • UG
   • MultiVCFAnalyzer
   • metagenomic post-processing
   • bcftools
2. Test (modern)
   • (singleref) supplied index
   • falco
   • fastp
   • convertBam
   • bwa mem
   • PrinSeq++
   • Kraken2
   • metagenomic post-processing
   • HC
3. Test (microbial genome)
   • (multipleref) refIndex
   • circular_mapper
   • KrakenUniq
   • HostRemoval
   • dedup
   • bedtools
   • rescaling
   • freebayes (+ bcftools)
4. Test (very short DNA)
   • (multipleref) supplied Index
   • mapAD
   • BBduk
   • MALT
   • metagenomic post-processing
   • PMDtools
   • ANGSD
5. Test (human poop-gen)
   • bam input baby
   • bowtie2
   • mapdamage
   • trimbam
   • mtnucratio
   • Pileupcaller
   • NucCont
   • SexDet

[TCLamnidis]

We also need a test that forces all possible merging steps, to ensure we don't create any file-name collisions. #986