fix: Adapt shell init for mamba 2

[jjerphan]

Description

Fix conda-forge/miniforge#697.

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?

---

I am interested to have some guidance on the best way to test it.

[conda-bot]

We require contributors to sign our Contributor License Agreement and we don't have one on file for @jjerphan.

In order for us to review and merge your code, please e-sign the Contributor License Agreement PDF. We then need to manually verify your signature, merge the PR (conda/infrastructure#1078), and ping the bot to refresh the PR.

[travishathaway]

@conda-bot check

[jaimergp]

I think you'll probably want some mamba specific tests in https://github.com/jjerphan/constructor/blob/fix/shell-init-on-mamba-2/examples/miniforge/test_install.sh.

[jaimergp]

Thanks!

[jjerphan]

Thank you for the guidance and the responsiveness.

[jjerphan]

@hmaarrfk: should we redo a PR on Miniforge to use 2.0.5 adding tests there for the installation on all platforms once a new version of constructor is released?

[hmaarrfk]

yes that would be great!

[jjerphan]

@jaimergp: how can we help with a new release of constructor?

[jaimergp]

We have a few items in the news/ dir, so we can try to cut something next week! WDYT @marcoesters? Are you planning any other PRs soon that would require waiting?

[marcoesters]

I think we should create a patch release for sure because of #922 at least. We can cut a release on Monday.

[jjerphan]

FYI, I am using now an installation of miniforge from the generated shell script without any problem.

I think it would help to add test on conda-forge/miniforge for all supported platforms.