IssueTracker

#### What you would like to accomplish:
Users observed that you can increase the timeout value of an event-driven v2 Cloud Function about the maximum value listed in the documentation [1]. If you deploy an event-driven v2 Cloud Function with a timeout value above 540 seconds (the maximum as per the documentation), the command fails, returning an output stating that the maximum timeout allowed is 540 seconds. If instead of that, you deploy the CF without setting a timeout value, then you can change the timeout value through the UI to a larger one, for example 1700 seconds.

#### How this might work:
Both the Cloud console and the gcloud command should not allow for such an update to occur. This could be done by introducing a validation of the timeout value.



[1] https://cloud.google.com/functions/quotas#:~:text=9%20minutes%20for%20event%2Ddriven%20functions.