RFC: Supporting spaces in paths as a first-class citizen

### Your question:

Presently, when users wish to install conda (miniforge/mambaforge or whatnot) it is always a mystery as to whether or not it will work if they have a "space" in their prefix.

One "package" that definitely doesn't work, is `Miniconda` and other related packages (`Miniforge`, `Mambaforge`)

It doesn't have to be that way.

My understanding, is that this is a question of escaping paths correctly.

However, I think this will require many packages to get patched upstream to ensure support.

I think one way to "solve this" (over a long period time) is to create a few images with a space in the build prefix, host prefix, and test prefix.

We would create a conda-forge.yml opt-in option, and start a mass migrator rebuilding all the packages.

Thoughts?