[Snyk] Fix for 2 vulnerabilities

[MaggieFero]

This PR was automatically created by Snyk using the credentials of a real user.

Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.

Changes included in this PR

• Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
  • requirements.txt

⚠️ Warning

opentelemetry-instrumentation-wsgi 0.37b0 has requirement opentelemetry-instrumentation==0.37b0, but you have opentelemetry-instrumentation 0.41b0.
opentelemetry-instrumentation-psycopg2 0.37b0 has requirement opentelemetry-instrumentation==0.37b0, but you have opentelemetry-instrumentation 0.41b0.
opentelemetry-instrumentation-django 0.37b0 has requirement opentelemetry-instrumentation==0.37b0, but you have opentelemetry-instrumentation 0.41b0.
opentelemetry-instrumentation-dbapi 0.37b0 has requirement opentelemetry-instrumentation==0.37b0, but you have opentelemetry-instrumentation 0.41b0.
opentelemetry-instrumentation-celery 0.37b0 has requirement opentelemetry-instrumentation==0.37b0, but you have opentelemetry-instrumentation 0.41b0.
opentelemetry-api 1.16.0 has requirement importlib-metadata>=5.0.0; python_version == "3.7", but you have importlib-metadata 4.13.0.
flower 2.0.0 requires tornado, which is not installed.
celery 5.3.0 requires kombu, which is not installed.
botocore 1.29.165 has requirement urllib3<1.27,>=1.25.4, but you have urllib3 2.0.6.

Vulnerabilities that will be fixed

By pinning:

Severity	Priority Score (*)	Issue	Upgrade	Breaking Change	Exploit Maturity
	50/1000 Why? Confidentiality impact: None, Integrity impact: None, Availability impact: Low, Scope: Unchanged, Exploit Maturity: No data, User Interaction (UI): None, Privileges Required (PR): None, Attack Complexity: Low, Attack Vector: Network, EPSS: 0.01055, Social Trends: No, Days since published: 0, Reachable: No, Transitive dependency: Yes, Is Malicious: No, Business Criticality: High, Provider Urgency: Medium, Package Popularity Score: 99, Impact: 2.35, Likelihood: 2.08, Score Version: V5	Regular Expression Denial of Service (ReDoS) SNYK-PYTHON-DJANGO-5932095	django: 3.2.20 -> 3.2.22	No	No Known Exploit
	170/1000 Why? Confidentiality impact: None, Integrity impact: None, Availability impact: High, Scope: Unchanged, Exploit Maturity: Proof of Concept, User Interaction (UI): None, Privileges Required (PR): None, Attack Complexity: Low, Attack Vector: Network, EPSS: 0.01055, Social Trends: No, Days since published: 0, Reachable: No, Transitive dependency: Yes, Is Malicious: No, Business Criticality: High, Provider Urgency: High, Package Popularity Score: 99, Impact: 5.99, Likelihood: 2.83, Score Version: V5	Uncontrolled Resource Consumption ('Resource Exhaustion') SNYK-PYTHON-OPENTELEMETRYINSTRUMENTATION-5926995	opentelemetry-instrumentation: 0.37b0 -> 0.41b0	No	Proof of Concept

(*) Note that the real score may have changed since the PR was raised.

Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.

Check the changes in this PR to ensure they won't cause issues with your project.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Regular Expression Denial of Service (ReDoS)

[MaggieFero]

We've already covered the Django upgrade they recommend here, and we could still take the pin (though I'll check first whether that might have been already addressed by one of our other upgrades by now). This PR also changes the Python version, though, as created by Snyk, and I think I'm going to remove that part, because the version they suggest isn't a bookworm, and that seems to be the release otherwise preferred.

[MaggieFero]

Snyk's proposed pin here turns out to be incompatible with our opentelemetry-celery pin, and we're already on this version of Flower, so there's nothing to merge here.