Fix bucket create to allow enough time for new bucket with same name to propagate

[modular-magician]

Fixes hashicorp/terraform-provider-google#11075

If a bucket is created with the same name as a bucket that was recently deleted, it can take 5-10 minutes to propagate. This change increases the Create timeout to 10 mins to reasonably allow enough time for that propagation to happen.

The issue here mainly presents itself when a ForceNew field is changed, like location, which is done in a few of our tests. The bucket is deleted and then recreated with the new config, but since the name remains the same, we have to wait for this propagation to happen.

If this PR is for Terraform, I acknowledge that I have:

• Searched through the issue tracker for an open issue that this either resolves or contributes to, commented on it to claim it, and written "fixes {url}" or "part of {url}" in this PR description. If there were no relevant open issues, I opened one and commented that I would like to work on it (not necessary for very small changes).
• Ensured that all new fields I added that can be set by a user appear in at least one example (for generated resources) or third_party test (for handwritten resources or update tests).
• Generated Terraform providers, and ran make test and make lint in the generated providers to ensure it passes unit and linter tests.
• Ran relevant acceptance tests using my own Google Cloud project and credentials (If the acceptance tests do not yet pass or you are unable to run them, please let your reviewer know).
• Read the Release Notes Guide before writing my release note below.

Release Note Template for Downstream PRs (will be copied)

storage: changed the default create timeout of `google_storage_bucket` to 10m from 4m

Derived from GoogleCloudPlatform/magic-modules#7314