feat: Wrapper and meta-wrapper for rbt consensus reads

[FelixMoelder]

Description

This adds two wrappers.
First a wrapper for rust-bio-tools consensus read calculation and second a meta wrapper which adds best practice post processing steps for consensus read calculation.

QC

• I confirm that:

For all wrappers added by this PR,

• there is a test case which covers any introduced changes,
• input: and output: file paths in the resulting rule can be changed arbitrarily,
• either the wrapper can only use a single core, or the example rule contains a threads: x statement with x being a reasonable default,
• rule names in the test case are in snake_case and somehow tell what the rule is about or match the tools purpose or name (e.g., map_reads for a step that maps reads),
• all environment.yaml specifications follow the respective best practices,
• wherever possible, command line arguments are inferred and set automatically (e.g. based on file extensions in input: or output:),
• all fields of the example rules in the Snakefiles and their entries are explained via comments (input:/output:/params: etc.),
• stderr and/or stdout are logged correctly (log:), depending on the wrapped tool,
• temporary files are either written to a unique hidden folder in the working directory, or (better) stored where the Python function tempfile.gettempdir() points to (see here; this also means that using any Python tempfile default behavior works),
• the meta.yaml contains a link to the documentation of the respective tool or command,
• Snakefiles pass the linting (snakemake --lint),
• Snakefiles are formatted with snakefmt,
• Python wrapper scripts are formatted with black.
• Conda environments use a minimal amount of channels, in recommended ordering. E.g. for bioconda, use (conda-forge, bioconda, nodefaults, as conda-forge should have highest priority and defaults channels are usually not needed because most packages are in conda-forge nowadays).

[johanneskoester]

I would not add such a generic rule to a meta-wrapper, as it can interfere with other sort rules in a workflow that uses the meta-wrapper. Rather make the rule very specific to the particular case you need here.

[FelixMoelder]

I changed it to a fixed directory and set an appropriate rule name.
Previously, that rule was used two times. First ensuring that the initial input of the workflow gets sorted and another time later within the workflow of meta wrapper.
Now, I changed the wrapper in a way that the initial bam file is expected to be presorted as an unsorted bam-file would require the sorting rule to be generic.