transfer packages from conda-forge to bioconda

This issue tracks a new procedure for transferring packages from conda-forge to bioconda. The plan is to test it out once and if it works, then formalize it in the docs.

Steps:

1. copy the artifacts from conda-forge to bioconda
2. mark them broken on conda-forge (a special procedure for conda-forge that removes them from the main label repodata, but keeps them available for lockfiles, explicit env exports, etc.)
3. add the package to bioconda
4. change the conda-forge recipe by having it be a simple metapackage that installs from bioconda via bioconda::

I think this would:

- fix solver priority issues so that everything is pulled from bioconda
- ensure that folks using only conda-forge can get at least get some sort of solver problem or issue or even an install of the package for updated versions
- ensure that folks using both bioconda and conda-forge can get updated versions
- avoid a circular dependence in the conda-forge feedstock on using bioconda to build a package (instead it is only used to point to bioconda via the metapackage, which is less fragile)

If this works, we'll formalize it in the docs.

To Do Items:

- [ ] try this with `r-nmf`
- [ ] copy the artifacts from conda-forge to bioconda
- [ ] mark them broken on conda-forge (a special procedure for conda-forge that removes them from the main label repodata, but keeps them available for lockfiles, explicit env exports, etc.) (https://github.com/conda-forge/admin-requests/pull/2014)
- [ ] add the package to bioconda (https://github.com/bioconda/bioconda-recipes/pull/64030)
- [ ] change the conda-forge recipe by having it be a simple metapackage that installs from bioconda via bioconda:: (https://github.com/conda-forge/r-nmf-feedstock/pull/27)
- [ ] possibly backfill old package versions with metapackages as well
- [ ] formalize in the docs if it works

xref: https://github.com/conda-forge/cfep/pull/52

cc @conda-forge/core for comments and advice