ci: Clean up Python 3.12 builds

[QuLogic]

PR summary

The final release is out, as are non-prerelease wheels, so we can drop those workarounds.

PR checklist

• [n/a] "closes #0000" is in the body of the PR description to link the related issue
• new and changed code is tested
• [n/a] Plotting related features are demonstrated in an example
• [n/a] New Features and API Changes are noted with a directive and release note
• [n/a] Documentation complies with general and docstring guidelines

[lumberbot-app]

Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

1. Checkout backport branch and update it.

git checkout v3.8.x
git pull

2. Cherry pick the first parent branch of the this PR on top of the older branch:

git cherry-pick -x -m1 6501209c3091898176b0a9179b32ad4edf9bf47e

3. You will likely have some merge/cherry-pick conflict here, fix them and commit:

git commit -am 'Backport PR #27059: ci: Clean up Python 3.12 builds'

4. Push to a named branch:

git push YOURFORK v3.8.x:auto-backport-of-pr-27059-on-v3.8.x

5. Create a PR against branch v3.8.x, I would have named this PR:

"Backport PR #27059 on branch v3.8.x (ci: Clean up Python 3.12 builds)"

And apply the correct labels and milestones.

Congratulations — you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon!

Remember to remove the Still Needs Manual Backport label once the PR gets merged.

If these instructions are inaccurate, feel free to suggest an improvement.

[QuLogic]

I think the backport conflict is probably just #27057 wasn't merged yet.

[QuLogic]

@meeseeksdev backport to v3.8.x

[lumberbot-app]

Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

1. Checkout backport branch and update it.

git checkout v3.8.x
git pull

2. Cherry pick the first parent branch of the this PR on top of the older branch:

git cherry-pick -x -m1 6501209c3091898176b0a9179b32ad4edf9bf47e

3. You will likely have some merge/cherry-pick conflict here, fix them and commit:

git commit -am 'Backport PR #27059: ci: Clean up Python 3.12 builds'

4. Push to a named branch:

git push YOURFORK v3.8.x:auto-backport-of-pr-27059-on-v3.8.x

5. Create a PR against branch v3.8.x, I would have named this PR:

"Backport PR #27059 on branch v3.8.x (ci: Clean up Python 3.12 builds)"

And apply the correct labels and milestones.

Congratulations — you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon!

Remember to remove the Still Needs Manual Backport label once the PR gets merged.

If these instructions are inaccurate, feel free to suggest an improvement.