Add support for shielded instance config on auto provisioned GKE nodes

[glindstedt]

part of hashicorp/terraform-provider-google#9180

Just now when I opening this PR I found out that this PR exists #6636 which is larger but does include what we need (being able to turn on secure boot). If you'd rather get that PR through feel free to close this, otherwise this PR offers a smaller chunk of those changes.

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)

container: Added support for Shielded Instance configuration for node auto-provisioning to `google_container_cluster`

[modular-magician]

Oops! It looks like you're using an unknown release-note type in your changelog entries:

• REPLACEME

Please only use the types listed in https://github.com/GoogleCloudPlatform/magic-modules/blob/master/.ci/RELEASE_NOTES_GUIDE.md.

[modular-magician]

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

I've detected that you're a community contributor. @c2thorn, 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, 86 insertions(+))
Terraform Beta: Diff ( 3 files changed, 86 insertions(+))
TF Validator: Diff ( 2 files changed, 3 insertions(+), 3 deletions(-))

[modular-magician]

Tests analytics

Total tests: 2211
Passed tests 1969
Skipped tests: 239
Failed tests: 3

Action taken

Triggering VCR tests in RECORDING mode for the tests that failed during VCR. Click here to see the failed tests

TestAccContainerCluster_nodeAutoprovisioningDefaultsShieldedInstance|TestAccBigQueryDataTable_bigtable|TestAccFirebaserulesRelease_BasicRelease

[modular-magician]

Tests passed during RECORDING mode:
TestAccBigQueryDataTable_bigtable[Debug log]
TestAccFirebaserulesRelease_BasicRelease[Debug log]

Tests failed during RECORDING mode:
TestAccContainerCluster_nodeAutoprovisioningDefaultsShieldedInstance[Error message] [Debug log]

Please fix these to complete your PR
View the build log or the debug log for each test

[c2thorn]

With all optional children, shielded_instance_config could be an empty block. Is there any significance in that? If not, could we add AtLeastOneOf to the children?

[glindstedt]

AFAIK there's no significance to having an empty block, so that would make sense. Should I update the schema in node_config.go.erb as well so they match?

[c2thorn]

looks like we missed that when adding to node_config... It's technically a breaking change to add it after it has already been released, so let's avoid it

[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, 94 insertions(+))
Terraform Beta: Diff ( 3 files changed, 94 insertions(+))
TF Validator: Diff ( 2 files changed, 3 insertions(+), 3 deletions(-))

[modular-magician]

Tests analytics

Total tests: 2214
Passed tests 1974
Skipped tests: 239
Failed tests: 1

Action taken

Triggering VCR tests in RECORDING mode for the tests that failed during VCR. Click here to see the failed tests

TestAccContainerCluster_nodeAutoprovisioningDefaultsShieldedInstance

[modular-magician]

Tests passed during RECORDING mode:
TestAccContainerCluster_nodeAutoprovisioningDefaultsShieldedInstance[Debug log]

All tests passed
View the build log or the debug log for each test