Rework documentation to use Miniforge instead of Anaconda

What is inaccurate?

We need to migrate RC from Anaconda to Miniforge due to changes in the Anaconda Terms of Service precluding use by any organization larger than 200 employees.

Hence all documentation related to Anaconda must be changed to reference and make use of Miniforge instead.

Where is the inaccuracy?

Please add locations in the comments and we will compile them in this issue.

• https://docs.rc.uab.edu/workflow_solutions/using_anaconda/#good-practice-for-finding-software-packages-on-anaconda needs heavy rewriting to get away from Anaconda. It should maybe become a separate tutorial!
• https://docs.rc.uab.edu/workflow_solutions/getting_containers/#create-your-own-docker-container needs rewriting to avoid usage of miniconda. There may be other uses in that file.

Useful boilerplate

Anaconda/Miniconda distribution

<!-- markdownlint-disable MD046 -->
!!! important

    The Anaconda and Miniconda software are subject to the Anaconda Terms of Service and may not be used for UAB business.
<!-- markdownlint-enable MD046 -->

Anaconda/R channels

<!-- markdownlint-disable MD046 -->
!!! important

    The `anaconda` and `r` channels are subject to the Anaconda Terms of Service and may not be used for UAB business. The `conda-forge` and `bioconda` channels are free to use.
<!-- markdownlint-enable MD046 -->

Start with the linked using_anaconda and getting_containers documentation pages, then search the repository for Anaconda, Miniconda, and related channel references. Review the existing guidance and the supplied boilerplate before updating every identified location to use Miniforge or approved alternatives. Done means no applicable documentation still directs UAB users to Anaconda or Miniconda.