Require CI to succeed on Python 3.12

[rmartin16]

Changes

• CI uses latest stable 3.12 release and tests are required to succeed now

Notes

• Python 3.12 is not available in Windows Store yet
• Running tests against Python 3.13 is not an option yet....and I'm not really sure when to expect it to be available...
• I'm not sure if there are bigger plans to incorporate m1 macOS testing yet...but feel free to supersede this PR

PR Checklist:

• All new features have been tested
• All new features have been documented
• I have read the CONTRIBUTING.md file
• I will abide by the code of conduct

[rmartin16]

will probably just wait on the win store and 3.13-dev unless a compelling reason to merge sooner presents

[freakboy3742]

We're obviously waiting for the 3.12 images to become available, but as soon as those are ready, this looks good.

I'm not sure what Steve Dower's plans are regarding the windows store version of 3.12; I'm happy to deal with that as a separate PR if it doesn't land before the 3.12 runner becomes available.e

I'm still trying to work out what we can do with M1 runners; there doesn't appear to be a free tier, so I need to work out what the cost will be if I turn those on. For now, I'm happy to live without M1 runners on Briefcase.

3.13.0a1 should land October 17, so it seems reasonable to assume the Python installation action will be updated a couple of days after that.

[rmartin16]

We're obviously waiting for the 3.12 images to become available, but as soon as those are ready, this looks good.

They landed this morning. These CI checks ran against Python 3.12.0.

I'm still trying to work out what we can do with M1 runners; there doesn't appear to be a free tier, so I need to work out what the cost will be if I turn those on. For now, I'm happy to live without M1 runners on Briefcase.

3.13.0a1 should land October 17, so it seems reasonable to assume the Python installation action will be updated a couple of days after that.

👍🏼