Upgrade django to 5.2

[annagav]

What are the relevant tickets?

Fix https://github.com/mitodl/hq/issues/8953

Description (What does it do?)

• Updating django 5.2

How can this be tested?

everything should work as expected

[github-actions]

OpenAPI Changes

Show/hide ## Changes for v0.yaml:

## Changes for v0.yaml:
No changes detected

## Changes for v1.yaml:
No changes detected

## Changes for v2.yaml:
No changes detected

Unexpected changes? Ensure your branch is up-to-date with main (consider rebasing).

[rhysyngsun]

Code review, will test shortly.

[rhysyngsun]

There are 2 migrations - 0022 and 0063 that are still using check=

[rhysyngsun]

I think going forward it might be better to have this be defined as a constraint within a minor version, so django>=5.2,<5.3. That way whenever a new patch comes down only the lockfile needs to be updated.

[Anas12091101]

I started reviewing this, but I see Nathan has already provided feedback and is testing it. I just have one small question; otherwise, I’ll leave the rest to him:

[Anas12091101]

Why was this method added, and how is it expected to be invoked? I don’t think aprocess_request is a recognized hook in Django middleware.

[rhysyngsun]

Good catch, I agree, I think it's something specific to RemoteUserMiddleware , it looks like MiddlewareMixin just calls sync_to_async on process_request() anyway: https://github.com/django/django/blob/stable/5.2.x/django/utils/deprecation.py#L125-L142