Upgrade to Python 3.14

@ulgens is already working on this.

Since Oct 18, 2025.

_Coming from https://github.com/django/djangoproject.com/pull/2234#issuecomment-3403185618_

I'm creating this task to investigate and understand is it possible to update the project to Python 3.14 and follow the related work if it is.

https://code.djangoproject.com/ticket/35844 mentions that

> Django 5.2 will be the first version to support Python 3.14

The current latest release of Trac is 1.6 and according to its trove classifiers, listed on https://pypi.org/project/Trac/1.6/, 3.11 is the latest Python version it supports.

@bmispelon's recommendation about the version compatibility between [djangoproject.com](https://github.com/django/djangoproject.com) and [code.djangoproject.com](https://github.com/django/code.djangoproject.com) can be found on https://github.com/django/djangoproject.com/pull/2234#issuecomment-3356263383

> I _think_ it's safe for the site and Trac to run separate Python versions. It's more important that they run the same Django version (because they share a database, and technically Django doesn't support running two different versions talking to the same db), but even that is not a hard requirement.

It seems Trac[ added support for Python 3.12](https://github.com/edgewall/trac/commit/ade1c041a29cc0319464721465e86c7be1159522) in their 1.6.1 but [according to their road map](https://trac.edgewall.org/milestone/1.6.1), those version is already 22 months late (and I'm not very hopeful about it will eventually come out - it seems the project is pretty close to be EOL'd.)

Considering all this data together, and assuming we want be on the safe side and use the same version for website and issue tracker, it seems Django 5.2 and Python 3.14 will be latest versions we can update the website to. To achieve any version update beyond that, we either need to somehow push the 1.6.1 release of Trac, fork the project and use the latest, or migrate away from Trac.

---

To sum up, when Django 5.2 supports 3.14, we can update the website to 3.14, but if we are going to keep using same Django version for issue tracker and website, we won't be able to update beyond 3.14.