Require at least Python 3.12 for the runner

[psss]

Pull Request Checklist

• implement the feature
• write the documentation
• include a release note

Resolve #5062.

[psss]

/packit test

[happz]

@psss is "test" in "... for the test runner" correct? I'd expct to read "tmt runner" or something similar.

[psss]

@psss is "test" in "... for the test runner" correct? I'd expct to read "tmt runner" or something similar.

Good point, let's directly use just the runner term as it's defined in the glossary. Updated in e5da12c.

[happz]

• As discussed yesterday evening on Slack, I believe [WIP] Bump minimum python requirements to 3.12 #5115 should be part of this PR or stack. Or we need to change the description and tone of this PR, since "Require at least Python 3.12 for the test runner" is not what this PR does. It updates docs, dropping mentions of Python 3.9-like distros as sutiable runners, but it does not change the actual tmt requirements. Once merged, I would still be able to install and run tmt from a Python 3.9 venv.
• To some extent [WIP] Bump minimum python requirements to 3.12 #5115 is already included in this stack, there is a significant overlap between [WIP] Bump minimum python requirements to 3.12 #5115 and Drop the typing_extensions requirement #5173.
• Drop the typing_extensions requirement #5173 is also misleading: its subject speaks about dropping typing_extensions, but the actual changes bump Python requirements.

It seems to me the changes are in the right direction, but separated into PRs in an unexpected way.

[LecrisUT]

Other than changing the title, looks ok. All of the ubuntu parts are still as ❓ but we can handle that later ™️

[psss]

Or we need to change the description and tone of this PR, since "Require at least Python 3.12 for the test runner" is not what this PR does.

Yeah, makes sense. I've bumped the required Python version in 4f5a515. The mypy and pyright versions intentionally kept at 3.9 to handle the related necessary changes in a separate pull request.