[Docs] Have Django release note updates be prioritized

When we do security releases, we publish the fix (with release notes) to all supported versions (currently main, 5.1, 5.0 and 4.2) at roughly the same time as us publishing the new version
We also publish a blog announcing the release and link the release notes

It takes a while for the docs to update (imagine this is a mixture of building and caching)
Last time it took about 1.5 hours before the release notes were updated

If it is possible, it would be great for the release notes to be updated quicker so that folks can see the information of the security release quicker (and the fellows can tell it "worked")

----

I mention security releases because normal releases have the fix and release notes merged before we publish a release and so these updates are available rather than us linking to empty release note pages

Start by tracing how release notes are built, deployed, and cached for the supported Django versions; the issue does not name specific files, tests, or entry points. Done means security-release notes become visible sooner after publication, with a way to verify that the update has completed.

Written by the indexing model from the issue text.