Update to Conda 23.7.2 & conda-libmamba-solver 23.7.0

[jakirkham]

Checklist

• Used a personal fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• Reset the build number to 0 (if the version changed)
• Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• Ensured the license file is being packaged.

[jakirkham]

cc @jaimergp @hmaarrfk

[jaimergp]

Unfortunately we need to wait for a hypothetical mamba 1.4.10 to include mamba-org/mamba#2732, which fixes #475.

[h-vetinari]

Unfortunately we need to wait for a hypothetical mamba 1.4.10 to include mamba-org/mamba#2732, which fixes #475.

Would also fix conda-forge/boa-feedstock#75, which is necessary to unblock some fixes in conda-build 3.26.

Edit: that's less of an issue for miniforge itself of course, I was talking more conda-forge in general...

[jaimergp]

It looks like it will be cut soon (today?): mamba-org/mamba#2766

[h-vetinari]

mamba 1.5.0 is live in conda-forge

[jaimergp]

mamba 1.5.0 available. Let's rerun.

[h-vetinari]

That's twice I snuck in juuust before you today (in my timezone) 😝

[h-vetinari]

I think this is somehow running into this constraint in mamba <1.4.4 on conda <23.4:
https://github.com/conda-forge/mamba-feedstock/blame/67d9230a2570dd951c84460da7fe2f0974bc3f6e/recipe/meta.yaml#L125

[h-vetinari]

Ah, and now you're back to conda-forge/boa-feedstock#75, because boa caps to mamba <1.4.2... 😑

[jakirkham]

Superseded by PR: #523