[Snyk] Fix for 6 vulnerabilities

[yu-iskw]

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/requirements.txt

⚠️ Warning

openapi-spec-validator 0.3.3 has requirement jsonschema<4.0.0,>=3.2.0, but you have jsonschema 4.17.3.
hologram 0.0.15 has requirement jsonschema<4.0,>=3.0, but you have jsonschema 4.17.3.
google-cloud-bigquery 2.34.4 has requirement protobuf<4.0.0dev,>=3.12.0, but you have protobuf 4.24.4.
dbt-bigquery 1.4.3 has requirement google-cloud-bigquery~=3.0, but you have google-cloud-bigquery 2.34.4.
black 23.3.0 has requirement packaging>=22.0, but you have packaging 21.3.
argcomplete 2.1.2 has requirement importlib-metadata<6,>=0.23; python_version == "3.7", but you have importlib-metadata 6.7.0.

Vulnerabilities that will be fixed

By pinning:

Severity	Priority Score (*)	Issue	Upgrade	Breaking Change	Exploit Maturity
	554/1000 Why? Has a fix available, CVSS 6.8	Insufficient Verification of Data Authenticity SNYK-PYTHON-CERTIFI-3164749	certifi: 2021.10.8 -> 2023.7.22	No	No Known Exploit
	704/1000 Why? Has a fix available, CVSS 9.8	Improper Following of a Certificate's Chain of Trust SNYK-PYTHON-CERTIFI-5805047	certifi: 2021.10.8 -> 2023.7.22	No	No Known Exploit
	499/1000 Why? Has a fix available, CVSS 5.7	Denial of Service (DoS) SNYK-PYTHON-PROTOBUF-3031740	protobuf: 3.18.0 -> 3.18.3	No	No Known Exploit
	519/1000 Why? Has a fix available, CVSS 6.1	Information Exposure SNYK-PYTHON-REQUESTS-5595532	requests: 2.27.1 -> 2.31.0	No	No Known Exploit
	509/1000 Why? Has a fix available, CVSS 5.9	Timing Attack SNYK-PYTHON-RSA-1038401	rsa: 4.5 -> 4.7	No	No Known Exploit
	509/1000 Why? Has a fix available, CVSS 5.9	Regular Expression Denial of Service (ReDoS) SNYK-PYTHON-SETUPTOOLS-3180412	setuptools: 44.1.1 -> 65.5.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:

🦉 Regular Expression Denial of Service (ReDoS)