DEP/TST: upgrade minimal requirement on pytest to 9.0.0 - #20810

Thank you for your contribution to Astropy! 🌌 This checklist is meant to remind the package maintainers who will review this pull request of some common things to look for.

• Do the proposed changes actually accomplish desired goals?
• Do the proposed changes follow the Astropy coding guidelines?
• Are tests added/updated as required? If so, do they follow the Astropy testing guidelines?
• Are docs added/updated as required? If so, do they follow the Astropy documentation guidelines?
• Is rebase and/or squash necessary? If so, please provide the author with appropriate instructions. Also see instructions for rebase and squash.
• Did the CI pass? If no, are the failures related? If you need to run daily and weekly cron jobs as part of the PR, please apply the "Extra CI" label. Codestyle issues can be fixed by the bot.
• Is a change log needed? If yes, did the change log check pass? If no, add the "no-changelog-entry-needed" label. If this is a manual backport, use the "skip-changelog-checks" label unless special changelog handling is necessary.
• Is this a big PR that makes a "What's new?" entry worthwhile and if so, is (1) a "what's new" entry included in this PR and (2) the "whatsnew-needed" label applied?
• At the time of adding the milestone, if the milestone set requires a backport to release branch(es), apply the appropriate "backport-X.Y.x" label(s) before merge.

Do we really need to backport?

not yet, but we'll want to the second a new test is bundled with a bugfix that needs pytest 9, and trust me, I've been waiting a whole year to use its features; such tests are coming

We don't usually bump minversion in backport unless we have no other choice...

we could not backport yet if you're not comfortable with it. I just don't understand the argument not to, at least not for a test-only dependency.

(and bear in mind that it might become necessary very soon anyway)

I think it makes more sense to bump this together with the backported code that actually needs it.

alright.
Is there any way to restart CircleCI other than the close/open dance ? I can't even seem to read the logs but I'm willing to bet it was the same transient network error I got with GHA at the same time.

You can restart it from CircleCI dashboard. I think it can read GH permission for the repo but I don't remember which access level give you the rerun button. I restarted them for you.

I don't think that's necessary, and I'd rather unblock his PR myself so he doesn't hold a grudge against me :D