If a user runs the config cmd before installing libmamba it can "brick" their installation. about conda-libmamba-solver

[jezdez]

In the current version of the solver plugin hook this is what happens:

(canary-2022-11-30) ~ via 🅒 canary-2022-11-30
❯ conda --version
conda 22.9.0+94.g887d03470
(canary-2022-11-30) ~ via 🅒 canary-2022-11-30
❯ conda config --set experimental_solver libmamba

CondaValueError: Key 'experimental_solver' is not a known primitive parameter.

(canary-2022-11-30) ~ via 🅒 canary-2022-11-30
❯ conda config --set solver libmamba
(canary-2022-11-30) ~ via 🅒 canary-2022-11-30
❯ conda install conda-libmamba-solver

CondaValueError: You have chosen a non-default solver backend (libmamba) but it was not recognized. Choose one of: classic
❯ conda config --set solver classic
(canary-2022-11-30) ~ via 🅒 canary-2022-11-30
❯ conda install conda-libmamba-solver
Collecting package metadata (current_repodata.json): done
Solving environment: done

## Package Plan ##

  environment location: /Users/jezdez/miniconda3-x86_64/envs/canary-2022-11-30

  added / updated specs:
    - conda-libmamba-solver
...