[ci] Increase timeout value for QEMU builds

[StrikerRUS]

Seem that previous bump (#4326) is not enough.

##[error]The job running on agent Hosted Agent ran longer than the maximum time of 150 minutes.
https://dev.azure.com/lightgbm-ci/lightgbm-ci/_build/results?buildId=10344&view=logs&j=c2f9361f-3c13-57db-3206-cee89820d5e3

[jameslamb]

wow 3 hours 😬

Ok I still think that won't be a problem at the current pace of development in this repo. If it becomes a problem maybe we should consider moving some of these to optional jobs triggered by comments in the future.

But for now, approved!

[StrikerRUS]

wow 3 hours 😬

Agree... 🙁

Typical pattern is simply set max allowed value

timeoutInMinutes: 360
https://github.com/search?l=YAML&p=1&q=qemu+timeoutInMinutes&type=Code

But unfortunately, long runs are related to QEMU itself (it is common practice to set timeout=360 for QEMU builds) because in those jobs all tests contribute to slowness.
#3948 (comment)

If it becomes a problem maybe we should consider moving some of these to optional jobs triggered by comments in the future.

... or just skip some tests there.

[github-actions]

This pull request has been automatically locked since there has not been any recent activity since it was closed. To start a new related discussion, open a new issue at https://github.com/microsoft/LightGBM/issues including a reference to this.