Upgrade Django (and related packages) to 4.2

[jacobtylerwalls]

Types of changes

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Description of Change

Django 3.2 will be end-of-life in April 2024. Since Arches 7.5 is an LTS, require the current Django LTS (4.2).

Upgrade Django-related dependencies.

Require Python 3.8 (see related docs update).

Fix some (not all) deprecation warnings to make it easier to get a clean test run with python -Werror manage.py test. Some deprecations are left for #9832 when Python 3.11 will be required.

Issues Solved

Closes #9799

Checklist

• Unit tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)

Ticket Background

• Sponsored by: Farallon Geographics
• Found by: @chiatt
• Tested by: @jacobtylerwalls

Further comments

• Elastic deprecations
• Django PR with changes to JSONField.get_db_prep_save():

This is probably easier to review commit by commit.

Upgrade instructions

In addition to usual steps like reinstalling all dependencies and running migrations, consider also:

• python manage.py makemigrations (before running migrations)
• remove USE_L10N setting
• change DEFAULT_FILE_STORAGE to STORAGES["default"]["BACKEND"]

[jacobtylerwalls]

@chiatt A handful of changes will be needed in projects e.g. afs (similar replacements of ugettext etc.)

I already have them prepared but haven't PR'd them to afs because it looks like afs isn't targeting Arches 7.5 yet.

[chiatt]

Thanks @jacobtylerwalls, could you document those changes in the release notes (releases/7.5.0.md) under "Upgrading an Arches Project"?

[jacobtylerwalls]

Done!

Should I also add the elastic changes this PR added to address deprecations? I don't know to what extent users are managing that themselves. We can also handle it later when actually upgrading elastic, but we might forget.

[apeters]

looks good to me!

[jacobtylerwalls]

Thanks for pushing this over the line!