Update to python 3.11

[hmaarrfk]

Closes #598
Closes #603

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.

[isuruf]

Merging and releasing a new miniforge will require macOS 10.13, so we need to make some changes in the README and maybe have an announcement.

[mbargull]

Merging and releasing a new miniforge will require macOS 10.13, so we need to make some changes in the README and maybe have an announcement.

I've added this to the tables in d2f7b3c .
Does that work for you?

So, a small announcement saying something like the following?

As announced in https://conda-forge.org/news/2023/08/24/bumping-minimum-macos-version-to-1013/ , the minimum supported macOS version has been raised to in 10.13 via conda-forge/conda-forge-pinning-feedstock#5829 for newly built packages and via #603 for the Miniforge installers.

(PR links could be replaced with dates/versions in case they are deemed to technical.)

[hmaarrfk]

Merging and releasing a new miniforge will require macOS 10.13, so we need to make some changes in the README and maybe have an announcement.

Great catch!

[hmaarrfk]

It seems that there is more traction on #603. closing in favor of Python 3.12.