conda-lock instructions are of the "conda / mamba" grouping but placed separately

[IAlibay]

Looking at the reworked docs, the conda-lock instructions are placed after single file installers & containers, but it's really just a specialised case of a conda (or mamba) install. Given this, my opinion is that it would be better to group it with the conda install section (possibly before the single file installer).

A good side effect of this would be that it would better align with the instructions we gave with the industry benchmarks, where we told folks to do the conda-lock install (so nearly everyone now has practice in doing so) and then default to the single file installer if that didn't work (which a few folks did). My assumption is that now our partners are more likely to want to use single file installers which is probably best for us (more reproducible etc...).

[mikemhenry]

Yes, from a support issue the nice thing about using a single file installer is that upstream changes will never break their env (or make so last week micromamba install openfe=1.3.0 worked but this week it doesn't since a new rdkit version breaks pytorch which breaks nagl)