Update to 24.1

[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.

[mbargull]

Since we have conda=24.3.0 already released upstream and I expect us to build conda-forge::conda=24.3.0 next week, maybe wait on that?
Not that it'd be bad to have 24.1-based installers; just seems odd to do it now :D.

[hmaarrfk]

i was confused as to why i thought i read your message badly. this can wait for 24.3. I guess it just didn't get released on conda-forge.

Not that it'd be bad to have 24.1-based installers; just seems odd to do it now :D.

We might find a bunch of bugs with 24.3. Historically Miniforge releases always had to wait for the dust to settle. So if this would have helped jakirkham, I would consider this a win right?

[hmaarrfk]

I'll leave this up till sunday or so, and I'll probably release unless I hear a strong objection or 24.3 gets released first

[mbargull]

hear a strong objection

None from my side.

or 24.3 gets released first

We'll build conda-build after the weekend and I'd expect conda to follow quickly.
We just avoid pushing out those build right before or during the weekend to not force anyone to fix issues during that time in case something does break.