Standardize documentation around deletion_protection, deletion_policy, force_deletion, etc

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
Please do not leave +1 or me too comments, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
If an issue is assigned to a user, that user is claiming responsibility for the issue.
Customers working with a Google Technical Account Manager or Customer Engineer can ask them to reach out internally to expedite investigation and resolution of this issue.

Terraform Version & Provider Version(s)

provider registry.terraform.io/hashicorp/google v6.11.0

Affected Resource(s)

google_bigquery_table
google_bigtable_instance
google_bigtable_table
google_container_cluster
google_looker_instance
google_project
google_redis_cluster
google_spanner_database
google_sql_database
google_sql_database_instance
google_storage_bucket

Terraform Configuration

Debug Output

No response

Expected Behavior

Looking across all of these different docs pages linked below, there is a ton of overlap in deletion_protection, deletion_policy, prevent_destroy, force_destroy, etc. While I understand that many of these differences in the arguments are not unique to the Terraform provider and are dictated by a lack of standardization upstream in the Google APIs, I do think that the documentation and explanation on the Terraform provider docs pages should be far more standardized and clear about things like:

which provide deletion protection on the Google API side of things vs just the internal Terraform provider side of things
which types of resources are protected by this for items that have downstream resources, eg:
- for buckets, needing to be forced to delete if they still contain objects
- for looker, what are the types of nested resources that prevent deletion? Does it prevent deletion of anything associated with the looker instance or just certain resources like the instance itself?
what the defaults are
what true and false mean
for the ones that have string values instead of bools, what the values mean
etc

Actual Behavior

Right now, all of the above expectations are very inconsistent across the various resources. Some resources have great documentation and are really clear on all those fronts and others are extremely vague and hard to decipher.

Also, there are likely other resources with this same problem that I did not flag when opening this issue, my search was not comprehensive.

hashicorp / terraform-provider-google