Update miniforge version used in installer for OSX

[hmaarrfk]

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]

Thanks Mark! 😄 Had a couple questions below

[jakirkham]

To provide more context to the earlier comments, was thinking something like this. So in the future we really only need to change a couple environment variables

[hmaarrfk]

Honestly, I do kinda see these repos as places where I would want to point other users to on how to "use" mamba/miniforge.

I don't think I want to install things to a "non-standard" directory yet given that we don't need to. The extra level of indirection is really annoying for new readers.

I think it is a bit of a shame that we can't find a common name for mambaforge and miniforge.

[hmaarrfk]

I would prefer avoiding a custom installation location, and avoiding an extra variable if we can.

[jakirkham]

How is it non-standard? Users are free to set the install path wherever is convenient. In some cases (particularly on systems where the home directory uses NFS), the default is not even a good idea.

[hmaarrfk]

I guess non-standard is the wrong word. It just seems "different" than what most people need.

The variable isn't really used beyond this 5 line script. So there is really no point in making it one in my mind.

Again, the main motivation in creating a variable for the version number is it bring it to the "front of the line of code" as opposed to the end of it highlighting its importance.

[hmaarrfk]

I think you are right. I just want to keep in sync with the anvil images. So I'm trying to follow
https://github.com/conda-forge/docker-images/blob/main/scripts/run_commands

[hmaarrfk]

seems to pass osx. i hope i got the uname correct,

[jakirkham]

@erykoff is this correct for macOS ARM? Or should we have something else here?

[erykoff]

Running uname -m on my machine does indeed say arm64.

[jakirkham]

Thanks for checking! 😄

[jakirkham]

Seems reasonable. Thanks for the updates Mark 😄

Suggested a change for sha256 (this should work on other platforms as well as long as they have openssl)

Not sure about macOS ARM, but asked someone who may know more above