[Snyk] Security upgrade aiohttp from 3.8.6 to 3.10.2

[q1blue]

Snyk has created this PR to fix 1 vulnerabilities in the pip dependencies of this project.

Snyk changed the following file(s):

• requirements.txt

⚠️ Warning

SQLAlchemy 2.0.32 has requirement typing-extensions>=4.6.0, but you have typing-extensions 4.5.0.
scikit-learn 1.0.2 requires scipy, which is not installed.
notebook 6.5.7 requires pyzmq, which is not installed.
mysql-connector-python 8.0.31 has requirement protobuf<=3.20.1,>=3.11.0, but you have protobuf 4.24.4.
jupyter-server 1.23.5 requires pyzmq, which is not installed.
jupyter-server-proxy 3.2.1 requires aiohttp, which is not installed.
jupyter-client 7.3.4 requires pyzmq, which is not installed.
ipykernel 6.15.0 requires pyzmq, which is not installed.
great-expectations 0.15.50 requires scipy, which is not installed.
dbt-core 1.4.8 has requirement click<8.1.4,>=7.0, but you have click 8.1.7.
azure-core 1.30.1 has requirement typing-extensions>=4.6.0, but you have typing-extensions 4.5.0.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.
• 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.

---

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
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

[changeset-bot]

⚠️ No Changeset found

Latest commit: ca11c98

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR