Add support for conda init --condabin, which adds condabin/ to PATH

[jaimergp]

Description

Closes #960.

Based on #943 to avoid conflicts down the line because this adds new options to construct.yaml. Excuse the diff while 943 gets reviewed.

Windows:

macOS:

Checklist - did you ...

• Add a file to the news directory (using the template) for the next release's release notes?
• Add / update necessary tests?
• Add / update outdated documentation?

[leofang]

Hello @jaimergp, thanks a ton for working on this, I've subscribed to this PR for some time and glad to see a momentum building up!

I have a use case for this, but I am not certain the PR as-is would help me once it's merged (mainly because I did not bother reading/understanding the codebase 😛). My use case is

• I get access to a remote Windows machine
• An admin-level account will execute my ansible playbooks to install things I need, including miniforge
• I log in as a user (with admin access too) after playbooks are executed. I expect at this point miniforge's conda is in my PATH so that I don't have to do anything to run conda create ....

Would this work? Thanks!

[jaimergp]

An admin-level account will execute my ansible playbooks to install things I need, including miniforge

Hey @leofang! Windows admin accounts are not allowed to modify PATH with these installers due to CVE-2022-26526. You can, however, run /path/to/installation/python.exe -m conda init --condabin in your ansible playbooks after the installation and it should work. Otherwise, I think you could also resort to this Ansible module?