feat(Cloud Storage): Enable uniform_bucket_level_access on Cloud Storage (GCS) static website sample

[mazgi]

Description

Fixes #<ISSUE-NUMBER>

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
• [x] 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://cloud.google.com/storage/docs/hosting-static-website

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

API enablement

• [x] 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~

[conventional-commit-lint-gcf[bot]]

🤖 I detect that the PR title and the commit message differ and there's only one commit. To use the PR title for the commit history, you can use Github's automerge feature with squashing, or use automerge label. Good luck human!

-- conventional-commit-lint bot https://conventionalcommits.org/

[mazgi]

/gcbrun

[glasnt]

/gcbrun

[glasnt]

/gcbrun