Bigtable: Add support for abandoning GC policy

[kevinsi4508]

Deleting a GC policy is not allowed in a replicated instance (an instance has more than one cluster).

Users who are running into this problem have to add an extra step to un-replicate the instance first before destroying all the resources.

With abandoning GC policy support, users can mark the GCP policy to be ABANDON. That way, the GC policy won't be deleted first, but will be deleted when the parent resource (table) is deleted.

fixes b/257991134

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).
• Generated Terraform, and ran make test and make lint to ensure it passes unit and linter tests.
• 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).
• Ran relevant acceptance tests (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)

bigtable: added support for abandoning GC policy

[modular-magician]

Hello! I am a robot who works on Magic Modules PRs.

I've detected that you're a community contributor. @megan07, a repository maintainer, has been assigned to assist you and help review your changes.

❓ First time contributing? Click here for more details

---

Your assigned reviewer will help review your code by:

• Ensuring it's backwards compatible, covers common error cases, etc.
• Summarizing the change into a user-facing changelog note.
• Passes tests, either our "VCR" suite, a set of presubmit tests, or with manual test runs.

You can help make sure that review is quick by running local tests and ensuring they're passing in between each push you make to your PR's branch. Also, try to leave a comment with each push you make, as pushes generally don't generate emails.

If your reviewer doesn't get back to you within a week after your most recent change, please feel free to leave a comment on the issue asking them to take a look! In the absence of a dedicated review dashboard most maintainers manage their pending reviews through email, and those will sometimes get lost in their inbox.

---

[modular-magician]

Hi there, I'm the Modular magician. I've detected the following information about your changes:

Diff report

Your PR generated some diffs in downstreams - here they are.

Terraform GA: Diff ( 3 files changed, 160 insertions(+))
Terraform Beta: Diff ( 3 files changed, 160 insertions(+))
TF Validator: Diff ( 2 files changed, 3 insertions(+), 3 deletions(-))

[modular-magician]

Tests analytics

Total tests: 2244
Passed tests 2002
Skipped tests: 242
Failed tests: 0

All tests passed in REPLAYING mode
View the build log

[kevinsi4508]

@kimihrr, could you also take a look when you get a chance. It is optional for you. Thanks!

[kevinsi4508]

Ping?

[shuyama1]

Test skipped in VCR. Kicked off an independent run: https://ci-oss.hashicorp.engineering/buildConfiguration/GoogleCloudBeta_ProviderGoogleCloudBetaMmUpstream/353692

Tests passed!

[shuyama1]

LGTM overall! Got a question regarding this feature: I assume after set "deletion_policy = ABANDON", deleting the instance will still delete the policy and leave no dangling resource?

[kevinsi4508]

LGTM overall! Got a question regarding this feature: I assume after set "deletion_policy = ABANDON", deleting the instance will still delete the policy and leave no dangling resource?

Yes, deleting an instance or the parent table will cascade delete their child GC Policies.

[shuyama1]

Thanks!