Apply Python 3.11 migration

[chrisburr]

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.

[conda-forge-linter]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

[chrisburr]

Cross-compilation needs conda-forge/cross-python-feedstock#56

[nicoddemus]

Thanks @chrisburr!

I see conda-forge/cross-python-feedstock#56 was merged, do we need to trigger something here now?

[chrisburr]

Looks like there are some cross-compilation issues to work out for Python 3.11, I'll look into it.

[chrisburr]

@conda-forge/pytest This should be ready to go (feel free to merge the bot's PR instead if you'd prefer, I just used this package for testing the migrator manually).

[h-vetinari]

It would be good to merge this as soon as feasible because a lot of feedstocks in the migration depend on this, but the migrator doesn't take that into account. This is because unfortunately the dependency graph for the migrator is built without test-only dependencies (which pytest almost always is), as that can lead to circularities (e.g. package A depending on B, and package B using A as a test-only dependency; this is not a build-level circularity, "just" on on recipe-level one).