deploy-runner-on-gcp - does the cloud region matter in relation to overall region?

### Describe the Bug

In the `deploy-runner-on-gcp` job called from `event-gather-pipeline.yml`, the `cml runner` option for `cloud-region` is hardcoded to `us-central1-f`. In my (very brief!) experience, this resulted in failures when attempting to create the machine due to `ZONE_RESOURCE_POOL_EXHAUSTED` - which may be transient, but I saw it repeatedly enough to [try a different cloud region that supports T4 GPUs](https://cloud.google.com/compute/docs/gpus/gpu-regions-zones#view-using-table).

As well, I specified a region of `us-west1` for my GCP project as a whole, different from the default `us-central1` region in CDP. That distinction---and the fact that `us-west1-b` cloud region worked for me---made me wonder whether this is a setting which needs to track the overall GCP region to ensure access to associated resources. I don't know enough about any of this to know whether that's true or if this machine is standalone.

### Expected Behavior

I expected the Event Gather action `deploy-runner-on-gcp` job to complete sucessfully.

### Reproduction

Stand up a CDP instance situated in a region other than `us-central1` and execute the Event Gather action.

### Environment

_Any additional information about your environment._

- OS Version: _[e.g. macOS 11.3.1]_
- Cookiecutter Version: _[e.g. 0.5.0]_