fix: wrap API-unordered TypeList attrs in toset() to prevent perpetual diffs

[cblecker]

Summary

• Several GKE resource attributes are modeled as TypeList in the Terraform provider, but the GKE API returns items in arbitrary order. This causes perpetual no-op diffs on every terraform plan.
• Wraps each affected value in toset() so Terraform treats them as order-insensitive, eliminating the spurious diffs.
• Edits the autogen template (autogen/main/cluster.tf.tmpl) and regenerates all module cluster.tf files, plus hand-edits the three non-generated gke module files.

Affected attributes

Attribute	Provider source
monitoring_config.enable_components	resource_container_cluster.go
logging_config.enable_components	resource_container_cluster.go
notification_config.filter.event_type	resource_container_cluster.go
node_config.tags	node_config.go
node_pool_auto_config.network_tags.tags	resource_container_cluster.go
cluster_autoscaling.auto_provisioning_defaults.oauth_scopes	resource_container_cluster.go

Attributes already TypeSet in the provider (no change needed): node_config.oauth_scopes, enable_k8s_beta_apis.enabled_apis.

Test plan

• Verify terraform validate passes against an example configuration
• Verify terraform plan no longer shows perpetual diffs for the affected attributes
• Confirm make generate produces no additional changes beyond those in this PR

[gemini-code-assist]

Code Review

This pull request updates various GKE cluster and node pool Terraform configurations to wrap list-based attributes—such as enable_components, oauth_scopes, tags, and event_type—with the toset() function. This ensures these attributes are treated as sets, preventing potential ordering issues or duplicate values. As there are no review comments provided, I have no feedback to offer.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[cblecker]

@apeabody sorry for the direct ping, but I'm wondering what the next steps might be to get this reviewed. thank you!

[apeabody]

/gcbrun