[Snyk] Security upgrade tensorflow from 1.14.0 to 2.12.0rc1

[WontonSam]

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.2.
tensorboard 1.14.0 has requirement setuptools>=41.0.0, but you have setuptools 40.5.0.
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.62.1 has requirement protobuf>=4.21.6, but you have protobuf 3.20.3.

Vulnerabilities that will be fixed

By pinning:

Severity	Priority Score (*)	Issue	Upgrade	Breaking Change	Exploit Maturity
	229/1000 Why? Confidentiality impact: None, Integrity impact: High, Availability impact: High, Scope: Unchanged, Exploit Maturity: Proof of Concept, User Interaction (UI): None, Privileges Required (PR): None, Attack Complexity: Low, Attack Vector: Network, EPSS: 0.0019, Social Trends: No, Days since published: 966, Reachable: No, Transitive dependency: Yes, Is Malicious: No, Business Criticality: High, Provider Urgency: Critical, Package Popularity Score: 99, Impact: 8.63, Likelihood: 2.64, Score Version: V5	Arbitrary File Write via Archive Extraction (Zip Slip) SNYK-PYTHON-TENSORFLOW-1315149	tensorflow: 1.14.0 -> 2.12.0rc1	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:

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

[github-actions]

This pull request has been marked as stale due to 60 days of inactivity. It will be closed in 1 week if no further activity occurs. If you think that’s incorrect or this pull request requires a review, please simply write any comment. If closed, you can revive the PR at any time and @mention a reviewer or discuss it on the dev@beam.apache.org list. Thank you for your contributions.

[github-actions]

This pull request has been closed due to lack of activity. If you think that is incorrect, or the pull request requires review, you can revive the PR at any time.