docs: Change Cloud Scheduler region from us-central1 to us-east1

[camiekim]

Description

Fixes b/507114306

Note: If you are not associated with Google, open an issue for discussion before submitting a pull request.

Checklist

Readiness

• [x ] Yes, merge this PR after it is approved
• No, don't merge this PR after it is approved

Style

• [x ] My sample follows the rules described for Terraform in the Effective Samples style guide
• My sample follows the other requirements and best practices in the Contributing
  guide

Testing

• [ x] I have performed tests described in the Contributing guide:

  • [ x] Tests pass: terraform apply
  • [ x] Lint pass: terraform fmt check

Intended location

• [ x] Yes, this sample will be (or already is) included on cloud.google.com
  Location(s): https://docs.cloud.google.com/scheduler/docs/schedule-run-cron-job-terraform

• No, this sample won't be included on cloud.google.com
  Reason:

API enablement

• If the sample needs an API enabled to pass testing, I have added the service to the Test setup file

Review

• If this sample adds a new directory, I have added codeowners to the CODEOWNERS file

[iennae]

/gcbrun

[iennae]

this needs some outside of the region tag changes to address timing issues since it's attempting to delete before it's ready. you could do something like this PR with the time_sleep and the null_resource to ensure that it doesn't attempt to delete to early 364192b#diff-d2d5e41ff94877d4a3388fbad8bf95dd71a3ef1e704d3f1d5d90fe4b5dd5cc1f

In a customer's environment they wouldn't be creating/deleting this quickly so it should be outside the region tag.

[camiekim]

Thanks, @iennae !