Update django from 3.2 to 4.2

[bart-maykin]

Checklist to prepare the Django 4.2 LTS upgrade

3rd party packages to verify/make compatible

• django-admin-index - ok
• django-better-admin-arrayfield -> needs to be replaced, see Replace django-better-admin-arrayfield open-formulieren/open-forms#3737 for the involved changes
• django-axes
  • version is okay
  • however, it is not specified as django-axes[ipware] so ipware is not pulled in, yet there are settings referring to ipware
  • possibly the reverse proxy setup is broken to determine the IP address because of this
  • it also uses legacy django axes settings like AXES_LOCK_OUT_BY_COMBINATION_USER_AND_IP
  • might just not be working properly at all
• django-choices - ok
• django-decorator-include - 3.1 support (passed tests with django 4.2.0)
• django-hijack - ok
• django-hijack-admin - not tested beyond 2.0 (passed tests with django 4.2.0 but can be removed)
• django-redis - ok
• django-rosetta - ok
• django-allauth - ok
• django-markdownx - 4.0.7 added support for Django 4,1 but not 4.2 yet (passed visual inspection for Django 4.2.0)
• django-markdownify - ok
• django-filter - ok
• django-timeline-logger - ok
• celery - ok
• django-celery-beat - ok
• maykin-django-two-factor-auth
• djangorestframework
• djangorestframework-camel-case - ok
• drf-spectacular - ok
• vng-api-common -> commonground-api-common - needs 4.2 support, and depends on drf-yasg etc. which is problematic
• elastic-apm - ok
• psycopg2 - current version is supported, upgrading to psycopg 3 is viable though
• sentry_sdk - ok
• zgw-consumers - ok