Removing Werkzeug from requirements-test

[i-oden]

Read this before submitting the PR

1. Always create a Draft PR first
2. Go through sections 1-5 below, fill them in and check all the boxes
3. Make sure that the branch is updated; if there's an "Update branch" button at the bottom of the PR, rebase or update branch.
4. When all boxes are checked, information is filled in, and the branch is updated: mark as Ready For Review and tag reviewers (top right)
5. Once there is a submitted review, implement the suggestions (if reasonable, otherwise discuss) and request an new review.

If there is a field which you are unsure about, enter the edit mode of this description or go to the PR template; There are invisible comments providing descriptions which may be of help.

1. Description / Summary

Solves Werkzeug vulnerability alerted via scans.

2. Jira task / GitHub issue

https://scilifelab.atlassian.net/jira/software/projects/DDS/boards/13/backlog?epics=visible&selectedIssue=DDS-2040

3. Type of change

What type of change(s) does the PR contain?

Check the relevant boxes below. For an explanation of the different sections, enter edit mode of this PR description template.

• New feature
  • Breaking: Why / How? Add info here.
  • Non-breaking
• Bug fix
• Security Alert fix
  • Package update
    • Major version update
• Documentation
• Workflow
• Tests only

4. Additional information

• Sprintlog Not adding sprintlog row since this only relates to tests.
• Blocking PRs
  • Merged
• PR to master branch: If checked, read the release instructions
  • I have followed steps 1-8.

5. Actions / Scans

Check the boxes when the specified checks have passed.

For information on what the different checks do and how to fix it if they're failing, enter edit mode of this description or go to the PR template.

• Black

• Pylint

• Prettier

• Yamllint

• Tests

• TestPyPI

• CodeQL

• Trivy

• Snyk

[rv0lt]

Why is it Werzeug needed in the tests in the client?

[i-oden]

Why is it Werzeug needed in the tests in the client?

I was asking myself the same thing. At some point I'm pretty sure we needed it because some package had it as a requirement but didn't install it itself, but now I'm not sure. Currently testing if it's needed.

[i-oden]

@rv0lt Seems like it's no longer needed. Updating the title of this PR

[rv0lt]

Runned the tests and seem to work!