feat: automatic conda environment handling

[lkstrp]

Changes proposed in this Pull Request

• Add option to let snakemake handle all conda environment handling based on pinned envs and os

• Makes it unneccessary for a user to wrangle with dependencys and envrionments at all

• Only snakemake would have to be installed. Then you could run snakemake ... --sdm conda and the

  • pinned env for your OS will be selected,
  • enabled if it already exists,
  • installed if it does not
  • and reinstalled if the file has changed.

A few things to discuss:

• Do we still want the option to use the base environment.yaml with snakemake (was the setting before, not sure if anyone uses it). Also it is not robust as only pinned envs are checked by the CI.
  • This could be implemented via a config setting (e.g. run.env=pinned and run.env=base).
    • I would rather not add this setting, because if --sdm conda is not added, the setting will do nothing.
• Which brings us to the option to add --sdm conda by default (or if set in config, e.g. deployment_method=pinned).
  • Would be a better config setting.
  • Not sure if this is possible with snakemake and good practice.
• Theoretically, you would just need to have snakemake installed, either in an env or in the base env. And everything would run and update itself.
  • At the moment this is not possible because _helpers.py needs some dependencies and is loaded before snakemake handles the environments. But this module would benefit from being broken up anyway.

Checklist

• I tested my contribution locally and it works as intended.
• Code and workflow changes are sufficiently documented.
• Changes in configuration options are added in config/config.default.yaml.
• Changes in configuration options are documented in doc/configtables/*.csv.
• A release note doc/release_notes.rst is added.

[FabianHofmann]

I find this a super nice and consistent approach! Perhaps we think about the case on how to deal with custom installations?