Update django requirement from ~=4.2.0 to ~=5.0

[dependabot]

Updates the requirements on django to permit the latest version.

Commits

• 617bcf6 [5.0.x] Bumped version for 5.0 release.
• 94914b5 [5.0.x] Finalized release notes for Django 5.0.
• 8e1b820 [5.0.x] Updated translations from Transifex.
• e4d7cc3 [5.0.x] Added release date for 4.2.8.
• cb013fc [5.0.x] Fixed #35002 -- Made UniqueConstraints with fields respect nulls_dist...
• 6c50273 [5.0.x] Fixed #35001 -- Fixed position of related widget action icons in admi...
• b8a476b [5.0.x] Improved wording in auth.models.User field docs.
• 471fa92 [5.0.x] Fixed #34995 -- Improved position of related widget's add link on adm...
• 9fe12b0 [5.0.x] Refs #34995 -- Made Selenium tests more robust for admin_views and ad...
• 7f1dc67 [5.0.x] Fixed #35006 -- Fixed migrations crash when altering Meta.db_table_co...
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[richardebeling]

• We need to wait for our dependencies to support Django 5 (?)
  • Unclear: django-extensions. There is a PR for django5 that fixes one async-problem and adds a django 5 CI run, however, it hasn't seen any activity in the last two months. We might be fine without the async-fix.
  • Unclear: django-fsm. There doesn't seem to be active maintenance, there are attempts to move it to Jazzband, but the maintainer doesn't seem to cooperate on that. One user made a fork called django-fsm-2, but it doesn't yet have documentation and/or list django5 support
  • Probably fine: mozilla-django-oidc (doesn't list officially supported django versions. It took them almost a year to make a release that "adds" django 4 support. Without large django changes in authentication, I don't think we have to wait for them)
  • Shouldn't be a problem:
    • pylint-django (pylint passes)
    • django-webtest (ci passes)
    • django-stubs (officially only support 4.2, but our CI passes. They have a PR for django 5 support)
    • django-toolbar (lists django 5.0 support as "pending", but their PR just added CI runs)
  • Isn't a problem: model-bakery (ci passes, they claim to support it)
• From the changelog, these look interesting:
  • Database generated model fields might be helpful with results: https://docs.djangoproject.com/en/5.0/releases/5.0/#database-generated-model-field
  • We might be able to simply some of our form field rendering in templates: https://docs.djangoproject.com/en/5.0/releases/5.0/#simplified-templates-for-form-field-rendering
  • test assertions for messages: https://docs.djangoproject.com/en/5.0/releases/5.0/#django-contrib-messages
• We should run the tests with deprecation warnings enabled and check if anything pops up

Apart from that, I don't see anything in the changelog that seems relevant to us.

I'd also bump psycopg to 3 since that's what the django docs recommend

[richardebeling]

Very interesting, upgrading to psycopg 3 causes SQL errors, did not expect that...

psycopg.errors.InvalidColumnReference: for SELECT DISTINCT, ORDER BY expressions must appear in select list
LINE 1: ...tion_participants"."evaluation_id" = $4) ORDER BY LOWER(NULL...

[richardebeling]

I created an issue with django out the psycopg3 problem here: https://code.djangoproject.com/ticket/35028 (cc @hansegucker)

Edit: The issue discussion implies a bug in django and that it's probably easiest for us to just stick with psycopg2 for now.

[niklasmohrin]

Dependencies: Kinda unsatisfying, but as long as our tests pass, I am fine. We should maybe consider dropping django-fsm anyways.
Psycopg: Sticking to version 2 seems like the right thing to do for now

[richardebeling]

@dependabot rebase

[dependabot]

Looks like this PR has been edited by someone other than Dependabot. That means Dependabot can't rebase it - sorry!

If you're happy for Dependabot to recreate it from scratch, overwriting any edits, you can request @dependabot recreate.