Improve the user setup experience for complex corporate environments

[schuylermartin45]

This issue tracks direct feedback recieved from PR #271

From @AaronOpfer:

• The make dev fails on up-to-date tooling if the conda-recipe-manager environment doesn't already exist as the conda command exits non-zero. I had to create a token env first to satisfy the makefile.
• The makefile doesn't work on my ancient CentOS7 make version 3.82. I needed to source make from conda-forge before I could proceed.
• Various tooling seems to be straddling defaults and conda-forge which is a no-no.
• Attempting to use the assisted build inside my company's conda configuration was impossible because we renamed all of the channels to make it more clear which ones are first-party vs third-party, and for various other reasons. As such every command that selects a specific conda channel (-c conda-forge) didn't work for me.

As of writing, it is unclear how much of this we can realistically tackle in the short-term. Given our limited resources on this project, I'm not sure if we can justify the time to handle such complicated corporate configurations. I don't think we will have a ton of users in this situation (as this serves as a development library for recipes, not a package delivery system), but I'm happy to be proven wrong.

Using defaults and conda-forge together is a stop-gap until defaults adds a few packages. So that is easily on the table.

I imagine a lot of this would be resolved if we also officially supported pixi.

[AaronOpfer]

Just to clarify, when I complained about straddling defaults and conda-forge, my desire was for the environment to solve on conda-forge alone, as it has no license encumbrance. In addition, in my corporate environment, I cannot use any build script that refers to specific conda channels by name (even command-lines like conda install -c conda-forge ...) without editing them first because all of our channel names are slightly different (we also two conda-forge channels: a mirror of the real one and one that is curated by conda_curation). Ideally, the package would work without any channel labels required on any solves.