Bump python precommit timeout to 3hrs

[aaltay]

Follow up to #10121

Regular version of the precommits are timing out. Not the pytest versions. Apply the same timeout to both places.

---

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

• Choose reviewer(s) and mention them in a comment (R: @username).
• Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
• If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

Post-Commit Tests Status (on master branch)

Lang	SDK	Apex	Dataflow	Flink	Gearpump	Samza	Spark
Go		---	---		---	---
Java
Python		---			---	---
XLang	---	---	---		---	---	---

Pre-Commit Tests Status (on master branch)

---	Java	Python	Go	Website
Non-portable
Portable	---		---	---

See .test-infra/jenkins/README for trigger phrase, status and link of all Jenkins jobs.

[udim]

run seed job

[aaltay]

Both @udim and @robertwb mentioned that this change does not help. Because there are some tests that got stuck/took a long time(?) and even with extended timeout tests still timeout. In the good case these tests do already fit in 2 hrs.

We can rollback this change based on the above observation. More important question would be, how are we going to identify which tests got stuck. So far we seem to be only able to see this issue in Jenkins environment and we have many hundreds of unit tests, running in 8 difference configurations.

[aaltay]

I still see : "21:11:51 Build timed out (after 120 minutes). Marking the build as aborted." I do not believe this timeout is actually doing what we expect. : https://builds.apache.org/job/beam_PreCommit_Python_Commit/10218/console

@yifanzou is this the right way to set timeout?