fix: Clone pip packages with environment

[jjerphan]

Description

Follow up of #4102 (comment).

Type of Change

• Bugfix
• Feature / enhancement
• CI / Documentation
• Maintenance

Checklist

• My code follows the general style and conventions of the codebase, ensuring consistency
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings
• I have run pre-commit run --all locally in the source folder and confirmed that there are no linter errors.
• I have added tests that prove my fix is effective or that my feature works
• New and existing tests pass locally with my changes

[codecov]

Codecov Report

❌ Patch coverage is 0% with 42 lines in your changes missing coverage. Please review.
✅ Project coverage is 51.10%. Comparing base (b98c281) to head (5cae6b0).

Files with missing lines	Patch %	Lines
libmamba/src/api/create.cpp	0.00%	36 Missing ⚠️
libmamba/src/api/utils.cpp	0.00%	6 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #4153      +/-   ##
==========================================
- Coverage   51.13%   51.10%   -0.04%     
==========================================
  Files         236      236              
  Lines       27645    27664      +19     
  Branches     2832     2833       +1     
==========================================
  Hits        14137    14137              
- Misses      13505    13524      +19     
  Partials        3        3              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[jjerphan]

Actually, it would be worth refactoring a few elements to reuse the code for exporting a YAML file specification from an environment and creating one from such a specification.

[jjerphan]

This is inspired from one of the install path, but we must not install those specifications modifying the configuration…

[jjerphan]

#4158 should come first.

[ifrh]

Cloning the pip packages would be realy cool.
And as side effect you perhals also solve

• unknown command "inspect" with pip < 22.2 #4075

If you create a micromamba environment for very old Python versions:

Python 2.7: Python has no -q so micromamba update prints Unknown option: -q
Python 3.4: for whatever reason a Pip version was installed by Micromamba which needs at least Python 3.5. Only if you specify the needed Pip version while creating the environment, a suitable pip persion for python 3.4 gets installed. I got some Pip in version 9.0, with that micromamba update prints ERROR: unknown command "inspect"
Python 3.5, Pip 20.3.4: micromamba update prints ERROR: unknown command "inspect"
Python 3.6, Pip 21.3.1: micromamba update prints ERROR: unknown command "inspect"
Python 3.7, Pip 22.3.1: micromamba update prints WARNING: pip inspect is currently an experimental command. The output format may change in a future release without prior warning.