[Snyk] Fix for 2 vulnerabilities

[rvema]

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-dev.txt

⚠️ Warning

torch 1.13.1 requires nvidia-cublas-cu11, which is not installed.
torch 1.13.1 requires nvidia-cuda-nvrtc-cu11, which is not installed.
torch 1.13.1 requires nvidia-cuda-runtime-cu11, which is not installed.
torch 1.13.1 requires nvidia-cudnn-cu11, which is not installed.
statsmodels 0.13.5 requires scipy, which is not installed.
statsmodels 0.13.5 requires scipy, which is not installed.
sphinx 5.3.0 has requirement docutils<0.20,>=0.14, but you have docutils 0.20.1.
sphinx-panels 0.6.0 has requirement sphinx<5,>=2, but you have sphinx 5.3.0.
scikit-learn 1.0.2 requires scipy, which is not installed.
s3fs 2023.1.0 has requirement aiobotocore~=2.4.2, but you have aiobotocore 1.4.2.
moto 4.2.7 requires werkzeug, which is not installed.
geopandas 0.10.2 requires pyproj, which is not installed.
Flask 2.2.5 requires Werkzeug, which is not installed.
flake8 5.0.4 has requirement importlib-metadata<4.3,>=1.1.0; python_version < "3.8", but you have importlib-metadata 6.7.0.
flake8 5.0.4 has requirement pycodestyle<2.10.0,>=2.9.0, but you have pycodestyle 2.10.0.
aiobotocore 1.4.2 has requirement botocore<1.20.107,>=1.20.106, but you have botocore 1.31.76.

Vulnerabilities that will be fixed

By pinning:

Severity	Priority Score (*)	Issue	Upgrade	Breaking Change	Exploit Maturity
	611/1000 Why? Recently disclosed, Has a fix available, CVSS 6.5	HTTP Request Smuggling SNYK-PYTHON-TORNADO-6041512	tornado: 6.2 -> 6.3.3	No	No Known Exploit
	661/1000 Why? Recently disclosed, Has a fix available, CVSS 7.5	Denial of Service (DoS) SNYK-PYTHON-WERKZEUG-6041510	werkzeug: 2.2.3 -> 3.0.1	No	No Known Exploit

(*) 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:

🦉 Denial of Service (DoS)

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}