[Snyk] Fix for 4 vulnerabilities

[mpast]

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

Snyk changed the following file(s):

• requirements.txt

⚠️ Warning

pyasn1-modules 0.3.0 has requirement pyasn1<0.6.0,>=0.4.6, but you have pyasn1 0.4.2.
google-gax 0.15.16 has requirement protobuf<4.0dev,>=3.0.0, but you have protobuf 4.24.4.
google-gax 0.15.16 has requirement google-auth<2.0dev,>=1.0.0, but you have google-auth 2.46.0.
google-cloud-vision 0.29.0 has requirement google-auth<2.0dev,>=1.0.2, but you have google-auth 2.46.0.
google-cloud-translate 1.3.3 has requirement google-api-core<2.0.0dev,>=1.6.0, but you have google-api-core 0.1.4.
google-cloud-translate 1.3.3 has requirement google-cloud-core<0.30dev,>=0.29.0, but you have google-cloud-core 0.28.1.
google-cloud-runtimeconfig 0.28.4 has requirement google-api-core<2.0.0dev,>=1.6.0, but you have google-api-core 0.1.4.
google-cloud-runtimeconfig 0.28.4 has requirement google-cloud-core<2.0dev,>=0.29.0, but you have google-cloud-core 0.28.1.
google-cloud-resource-manager 0.28.4 has requirement google-api-core<2.0.0dev,>=1.6.0, but you have google-api-core 0.1.4.
google-cloud-resource-manager 0.28.4 has requirement google-cloud-core<2.0dev,>=0.29.0, but you have google-cloud-core 0.28.1.
google-cloud-pubsub 0.30.1 has requirement google-auth<2.0dev,>=1.0.2, but you have google-auth 2.46.0.
google-api-python-client 2.187.0 has requirement google-api-core!=2.0.*,!=2.1.*,!=2.2.*,!=2.3.0,<3.0.0,>=1.31.5, but you have google-api-core 0.1.4.
google-api-core 0.1.4 has requirement google-auth<2.0.0dev,>=0.4.0, but you have google-auth 2.46.0.
Flask 1.0.2 requires Werkzeug, which is not installed.

---

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:

🦉 Improper Control of Generation of Code ('Code Injection')
🦉 Directory Traversal