Why are we making this change?

Some of our users prefer that their mission critical clusters be not deleted unintentionally. This change allows them to do that.

What

Expose deletion protection as a field. Input is piped directly to deletion_protection field in google_container_cluster

Testing

• Created a cluster with deletion protection disabled, verified it could be torn down with gcluster destroy
• Created a cluster with deletion protection enabled, verified gcluster destroy threw an error
• Set deletion protection = false on above cluster, applied. Then ran gcluster destroy and verified cluster was torn down

Submission Checklist

NOTE: Community submissions can take up to 2 weeks to be reviewed.

Please take the following actions before submitting this pull request.

• Fork your PR branch from the Toolkit "develop" branch (not main)
• Test all changes with pre-commit in a local branch #
• Confirm that "make tests" passes all tests
• Add or modify unit tests to cover code changes
• Ensure that unit test coverage remains above 80%
• Update all applicable documentation
• Follow Cluster Toolkit Contribution guidelines #