chore: Upgrade Django to 4.2.x

[arslanashraf7]

What are the relevant tickets?

#1467, https://github.com/mitodl/hq/issues/3747

What's this PR do?

• Upgrades Django to 4.2. You can check the release notes for Django 4 on https://docs.djangoproject.com/en/5.0/releases/4.0/
• In the process of upgrading, this PR also upgrades other major packages like postgres, django-hijack, oauth-toolkit, celery, celery-redbeat, django-robots, djangorestframework
• In the process of upgrading several packages to their major version the PR also adds/removes some existing unused settings
• It also fixes the existing migrations
• It removes our dependency on pytz package because pytz has been deprecated and Its support would be removed in Django 5.x.
• It also updates tests
• It also updates all the dependencies form ol-django
  NOTE:
• Django hijack would not work out of the box until it has some specific state being set in the session. So, I have created a new support middleware in order to make sure that Django hijack works properly.

How should this be manually tested?

• Testing on existing instance
• Setup your app on the master branch, run seed commands to pre-fill the data (configure_cms & seed_data)
• Create some bootcamps, BootCamp runs, BootCamp applications, certificates, invitation letters etc
• run different commands e.g. set_appication_state you can also use this command in testing for setting application state from initial to completion and inbetween

Where should the reviewer start?

Setup a good amount of data on the master branch before moving to this branch. You should have users, profiles, applications, application steps etc.

What GIF best describes this PR or how it makes you feel?

[gitguardian]

⚠️ GitGuardian has uncovered 4 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
433857	Triggered	Generic Password	80feb61	authentication/pipeline/user_test.py	View secret
433857	Triggered	Generic Password	80feb61	authentication/pipeline/user_test.py	View secret
433857	Triggered	Generic Password	80feb61	authentication/pipeline/user_test.py	View secret
433857	Triggered	Generic Password	80feb61	authentication/pipeline/user_test.py	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[asadali145]

LGTM! Just a couple of minor things.

I have noticed an exception that does not impact any functionality. It exists on the current master.
Simply go to the CMS Dashboard, you will see an exception in local logs.

Will look like:

Traceback (most recent call last):
web-1     |   File "/opt/venv/lib/python3.10/site-packages/django/template/base.py", line 886, in _resolve_lookup
web-1     |     if isinstance(current, BaseContext) and getattr(
web-1     | AttributeError: type object 'Context' has no attribute 'header_controls'
web-1     | 
web-1     | During handling of the above exception, another exception occurred:
web-1     | 
web-1     | Traceback (most recent call last):
web-1     |   File "/opt/venv/lib/python3.10/site-packages/django/template/base.py", line 896, in _resolve_lookup
web-1     |     current = current[int(bit)]
web-1     | ValueError: invalid literal for int() with base 10: 'header_controls'
web-1     | 
web-1     | During handling of the above exception, another exception occurred:
web-1     | 
web-1     | Traceback (most recent call last):
web-1     |   File "/opt/venv/lib/python3.10/site-packages/django/template/base.py", line 903, in _resolve_lookup
web-1     |     raise VariableDoesNotExist(

[asadali145]

Suggested change

	from django.urls import re_path
	from django.urls import path
	from django.urls import path, re_path

[asadali145]

Suggested change

	We will probably need to add a more robust solution to django-hijack package."""
	We will probably need to add a more robust solution to django-hijack package.
	"""

[asadali145]

Can we mention that the issue was with the notification injection? I believe that was the only issue?

[asadali145]

This can also be a simple path like below paths.