[Snyk] Security upgrade tensorflow from 1.14.0 to 2.11.1

[SvcGithubAppSecAutomation]

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:
  • sdks/python/apache_beam/testing/benchmarks/chicago_taxi/requirements.txt

⚠️ Warning

tensorflow-model-analysis 0.13.2 has requirement ipywidgets<8,>=7, but you have ipywidgets 8.1.0.
tensorboard 1.14.0 has requirement setuptools>=41.0.0, but you have setuptools 39.0.1.
notebook 5.7.16 has requirement nbconvert<6.0, but you have nbconvert 7.6.0.
jupyter-console 6.6.3 has requirement jupyter-client>=7.0.0, but you have jupyter-client 6.2.0.
grpcio-status 1.56.2 has requirement protobuf>=4.21.6, but you have protobuf 3.20.3.
google-auth 2.22.0 has requirement urllib3<2.0, but you have urllib3 2.0.4.

Vulnerabilities that will be fixed

By pinning:

Severity	Priority Score (*)	Issue	Upgrade	Breaking Change	Exploit Maturity
	731/1000 Why? Proof of Concept exploit, Has a fix available, CVSS 8.2	Uninitialized Memory Exposure SNYK-PYTHON-TENSORFLOW-1050413	tensorflow: 1.14.0 -> 2.11.1	No	Proof of Concept
	701/1000 Why? Proof of Concept exploit, Has a fix available, CVSS 7.6	Heap-based Buffer Overflow SNYK-PYTHON-TENSORFLOW-2393361	tensorflow: 1.14.0 -> 2.11.1	No	Proof of Concept
	711/1000 Why? Proof of Concept exploit, Has a fix available, CVSS 7.8	Remote Code Execution (RCE) SNYK-PYTHON-TENSORFLOW-2841408	tensorflow: 1.14.0 -> 2.11.1	No	Proof of Concept
	721/1000 Why? Proof of Concept exploit, Has a fix available, CVSS 8	Double Free SNYK-PYTHON-TENSORFLOW-3372999	tensorflow: 1.14.0 -> 2.11.1	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:

🦉 Remote Code Execution (RCE)