djangoci PR builds using outdated Python versions

[Mike Edmunds]

The Jenkins PR builds are using outdated Python versions: 3.12.2, 3.12.7, 3.13.0.rc3, and 3.13.0. The latest releases are 3.12.9 and 3.13.2 (both 2025-02-04).

Since "We highly recommend and only officially support the latest release of each series," it seems like tests should be running on them. (Or at least, not on prereleases. And 3.12.2 is over a year old.)

To verify:

1. Choose any recent PR at ​https://github.com/django/django/pulls. (I can't link to specific PR builds here, because Jenkins logs are purged very quickly.)
2. Scroll down to the "All checks have passed" or "Some checks were not successful" block in the PR.
3. In the checks list, click into any of the djangoci jobs (identified by a Django logo—e.g., pr-mariadb, pull-requests-focal, etc.).
4. On the Jenkins page, click "Console Output." If there's a "Full log" link above the output, click it to expand the setup logs.
5. Search the log for "created virtual environment" and note the Python version.

Results:

• CPython3.12.2.final.0-64 (e.g., pull-requests-focal/database=mysql,label=focal-pr,python=python3.12)
• CPython3.12.7.final.0-64 (e.g., pull-requests-focal/database=postgres,label=focal-pr,python=python3.12)
• CPython3.13.0.candidate.3-64 (e.g., pull-requests-focal/database=sqlite3,label=focal-pr,python=python3.13)
• CPython3.13.0.final.0-64 (e.g., pr-mariadb/database=mysql,label=mariadb,python=python3.13)

[Apologies if this is the wrong place to report djangoci configuration issues. I did try asking in the forum.]