Upgrade python and django

[mbertrand]

Pre-Flight checklist

• Testing
  • Code is tested
  • Changes have been manually tested

What are the relevant tickets?

Closes #3724

What's this PR do?

• Upgrades python to 3.11, Django to 4.1
• Fixes tests and functionality that broke as a result of the above

How should this be manually tested?

Basically test everything. In particular:

• registration, login, logout, forgot password

• hijacking users

• make posts and comments

• backpopulate course data (edx or ocw or xpro, pick whatever you like).

• search

• micromasters/open-discussions integration is a bit tricky to test locally, I was planning to leave this for RC.

Any background context you want to provide?

• The moto version update doubled the python unit test time, but then I realized a few global fixtures that use moto were being unnecessarily called for every test via autouse=true. Fixing that dropped total python test time to normal.
• djangorestframework-jwt (used for authentication between micromasters and open) has not been updated since 2017 and isn't compatible with python 3.11. A drop-in replacement package (drf-jwt) was used for this PR, but at some point we should probably switch to djangorestframework_simplejwt instead.
• The gitguardian alerts are for betamax cassette files created/modified when running tests against the local reddit instance.
• The django-hijack version update required a new template file, removal of django-hijack-admin, and some changes to how a hijacked user is detected. The UI that indicates you are logged in as a hijacked user looks different now.

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

[gitguardian]

⚠️ GitGuardian has uncovered 11 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	Secret	Commit	Filename
6852801	Bearer Token	67048f3	cassettes/channels.views.posts_test.test_get_removed_post[staff_user-200].json	View secret
6852801	Bearer Token	67048f3	cassettes/channels.views.posts_test.test_get_removed_post[staff_user-200].json	View secret
6852801	Bearer Token	67048f3	cassettes/channels.views.posts_test.test_get_removed_post[staff_user-200].json	View secret
6852801	Bearer Token	67048f3	cassettes/channels.views.posts_test.test_get_removed_post[staff_user-200].json	View secret
6852802	Bearer Token	67048f3	cassettes/channels.views.posts_test.test_get_removed_post[staff_user-200].json	View secret
6852802	Bearer Token	67048f3	cassettes/channels.views.posts_test.test_get_removed_post[staff_user-200].json	View secret
6852803	Bearer Token	67048f3	cassettes/channels.views.posts_test.test_get_removed_post[user-404].json	View secret
6852803	Bearer Token	67048f3	cassettes/channels.views.posts_test.test_get_removed_post[user-404].json	View secret
6852804	Bearer Token	67048f3	cassettes/channels.views.posts_test.test_get_removed_post[user-404].json	View secret
6852804	Bearer Token	67048f3	cassettes/channels.views.posts_test.test_get_removed_post[user-404].json	View secret
6852804	Bearer Token	67048f3	cassettes/channels.views.posts_test.test_get_removed_post[user-404].json	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.

---

<sup>🦉 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.

Our GitHub checks need improvements? Share your feedbacks!</sup>

[abeglova]

LGTM Everything i tested worked great

[mbertrand]

Note for future reference: I did not upgrade django beyond 4.1.x because django 4.2+ requires PostgreSQL 12+

[mbertrand]

Additional notes:

• Updated celery/sentry to get rid of an excepton logging exception (AttributeError: '_Code' object has no attribute 'co_positions' getsentry/sentry-python#1798)

• Updated attrs to get rid of a warning when running backpopulate__data commands

• Updated google-api-python-client to fix youtube video syncing

• Updated pylint to avoid false import errors with os, io