As previously discussed with @ngompa - rather than having to figure out an upgrade policy for Django in EPEL, and potentially doing incompatible upgrades, we should rather only package Django LTS releases (and we can retire them when they reach EOL provided a replacement is available).

The outgoing LTS, 3.2 is EOL this month (April 2024), so we should start packaging python-django4.2. In the future the plan is to branch python-djangoX.Y from Fedora each time an LTS release is cut - whether taking the latest X.Y commit in Fedora and cherry-picking spec improvements, or taking the latest Fedora spec and downgrading.