fix!: pin dependency version in all wrapper conda env yamls

[tedil]

This PR aims to increase reproducibility and is a precursor to be able to properly end-to-end test the pipeline.
All version specifications in the wrappers' environment.yaml files were pinned to one specific version, in a configuration that can actually be installed with mamba/conda and a strict channel priority (which is why sometimes the channel definitions were also changed).
This was done programmatically, with the exception of some wrappers for which manual intervention was required:

• gcnv
• jaffa/run
• cnvetti/on_target/postprocess
• svtk
• scramble
• link_in_bam
• lohhla

Since there are no tests for the wrappers yet, I can't really be sure if this breaks anything, so I'd rather be cautious and assume that it does.

[coveralls]

coverage: 85.764%. remained the same
when pulling 7796eed on wrapper-versioning
into e008e7e on main.

[Nicolai-vKuegelgen]

From my understanding the 'r' channel should not be used anymore, also some packages use 'r' as a package name instead of r-base.

I don't think "http://conda.cubi.bihealth.org/cubiconda" is reachable from the outside, so relying on that here is a bit unfortunate (no easy way to fix this though, I guess)

[Nicolai-vKuegelgen]

LGTM overall

However, this covers many more steps than I am familiar with, so can't guarantee that this won't break anything.

[ericblanc20]

Looks good to me

[tedil]

@Nicolai-vKuegelgen @ericblanc20 as long as the default rerun-triggers are used (which are currently set to ["mtime", "params", "input"] I think), this should not trigger re-runs for existing pipelines -- for that, the rerun-trigger software-env would have to be included (or of course all). So I believe this should be safe to merge without impacting any existing projects.