Bump werkzeug 3.0.0 to 3.0.6 in tests and integration tests (#1672)

### Feature or Bugfix
- Bugfix

### Detail
Bumps [werkzeug](https://github.com/pallets/werkzeug) from 3.0.3 to
3.0.6.

### Relates

### Security
Please answer the questions below briefly where applicable, or write
`N/A`. Based on
[OWASP 10](https://owasp.org/Top10/en/).

- Does this PR introduce or modify any input fields or queries - this
includes
fetching data from storage outside the application (e.g. a database, an
S3 bucket)?
  - Is the input sanitized?
- What precautions are you taking before deserializing the data you
consume?
  - Is injection prevented by parametrizing queries?
  - Have you ensured no `eval` or similar functions are used?
- Does this PR introduce any functionality or component that requires
authorization?
- How have you ensured it respects the existing AuthN/AuthZ mechanisms?
  - Are you logging failed auth attempts?
- Are you using or adding any cryptographic features?
  - Do you use a standard proven implementations?
  - Are the used keys controlled by the customer? Where are they stored?
- Are you introducing any new policies/roles/users?
  - Have you used the least-privilege principle? How?


By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache 2.0 license.

tests/requirements.txt

@@ -4,5 +4,5 @@ pytest-cov==3.0.0
 pytest-mock==3.6.1
 pytest-dependency==0.5.1
 httpx==0.27.2
-werkzeug==3.0.3
+werkzeug==3.0.6
 assertpy==1.1.0

tests_new/integration_tests/requirements.txt

@@ -7,5 +7,5 @@ pytest-mock==3.6.1
 pytest-dependency==0.5.1
 requests==2.32.2
 dataclasses-json==0.6.6
-werkzeug==3.0.3
+werkzeug==3.0.6
 retrying==1.3.4