Add missing migration for Partners & AssignedReviewers (#4804)

Related to #4790. I missed an edge case where an `AssignedReviewer` was
also a Partner, in which the migrations would fail as the `type`
attribute is protected in the model. This moves all types of partner to
reviewer.

---------

Co-authored-by: Fredrik Jonsson <frjo@xdeb.org>

Update packages in translate-cpu.txt. (#4741)

Update all locale po files and the pot file. (#4714)

Update to Django 5.2 LTS and Wagtail 7 LTS (#4666)

Fixes #4250

These are big updated so everything needs to be tested.

Things to test:

- [x] The complete login procedure.
    - [x] With enforce 2FA
    - [ ] For staff via Google
    - [x] Without password
    - [x] With password
    - [x] Forgot password
    - [x] Change password
- [x] Add and remove 2FA
- [x] The complete submission process for new and for old users.
- [x] The complete review process for reviewers and for staff.
- [x] Alla kind of file uploads and downloads. Do they work and do they
have the correct permissions.
- [x] Permissions for all important views.
- [x] Notifications via slack, e-mail etc.

Fix wagtail 2FA disable confirm button styling (#4649)

swapped `btn` for wagtail's `button` class

Fixed old status name showing twice in a transition notification (#4621)

<!--
Thanks for contributing to Hypha!

Please ensure your contributions pass all necessary linting/testing and
that the appropriate documentation has been updated.
-->

<!--
Describe briefly what your pull request changes. If this is resolving an
issue, please specify below via "Fixes #<Github Issue ID>"
-->
Fixes #4616. After updating to django-viewflow it looks like the
application status doesn't get updated until after the notification is
sent, when before this would happen before. Thus, getting the current
application status as the "new phase" resulted in a duplicate of the
"old phase", ie. `<USER> has updated the status of <APPLICATION>: Need
screening → Need screening`

## Test Steps
<!-- 
If step does not require manual testing, skip/remove this section.

Give a brief overview of the steps required for a user/dev to test this
contribution. Important things to include:
 - Required user roles for where necessary (ie. "As a Staff Admin...")
- Clear & validatable expected results (ie. "Confirm the submit button
is now not clickable")
- Language that can be understood by non-technical testers if being
tested by users
-->

- [ ] Ensure slack & email notifications for application transitions
represent the actual transition that took place

Removed nested htmx triggering submission export on search (#4597)

Fixes #4545.

Removed the nested htmx that was triggering CSV exporting on query search or altering of draft/archive sliders.

Fix report file path issue and duplicate file issue, Fix file path is…

…sue for Project and SOW Form (#4580)

Fixes #4574 

As reports are project documents so we added a different path for its
files but we used ReportVersion instance checks and missed Report
instances so reports files and its version files were having different
path and were creating issues. We could solve it in that way as well but
I realise as projects are also the extension of submission and we have
been trying to merge them so keep everything similar with same url
pattern.

Now it uses submission id to generate path and render the file similar
to other submission files.

Now, it also handles the duplicate file issue on every upload. It was
resolved for the application form but not for the report forms.

E-mail template whitespace improvements (#4551)

Update python packages. (#4523)