Update test dependencies

[tmorrell]

:heart: Thank you for your contribution!

Description

Update versions so tests pass

Checklist

Ticks in all boxes and 🟢 on all GitHub actions status checks are required to merge:

• [x] I'm aware of the code of conduct.
• [x] I've created logical separate commits and followed the commit message format.
• [x] I've added relevant test cases.
• [x] I've added relevant documentation.
• [x] I've marked translation strings (for relevant code).
• [x] I've followed the CSS/JS and React guidelines (for relevant code).
• [x] I've followed the web accessibility guidelines (for relevant code).
• [x] I've followed the user interface guidelines (for relevant code).
• [x] I've identified the copyright holder(s) and updated copyright headers for touched files (>15 lines contributions).
• [x] I've NOT included third-party code (copy/pasted source code or new dependencies).

Third-party code

If you've added third-party code (copy/pasted or new dependencies), please reach out to an architect.

Reminder

By using GitHub, you have already agreed to the GitHub’s Terms of Service including that:

1. You license your contribution under the same terms as the current repository’s license.
2. You agree that you have the right to license your contribution under the current repository’s license.

[tmorrell]

I'm also going to narrate a bit as PR coordinator. I know kpsherva is away this week, so I'm going to swap CERN reviewers and add nicola. I'm leaving this in the "in review/discussion" column, although you could argue we're just waiting for an additional review.

I'm not sure what mechanism works best for managing reviews - should we expect reviewers to look at the board or should the coordinator directly assign reviewers? I'm trying the latter for the next week.

[ntarocco]

I moved the PR to the approved column (should I have done that? :))