potential fix for gke provider upgrade problem

[modular-magician]

Removed the DSF and set the fields to O+C. Tested it locally and it should fix the problem.

This resolves hashicorp/terraform-provider-google#12422 and resolves hashicorp/terraform-provider-google#12549

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: fixed a bug where upgrading provider version breaks on `node_pool_auto_config` or `node_pool_defaults` 

Derived from GoogleCloudPlatform/magic-modules#6546

[thameezb]

4.38.0 has been released, and the issue still persists on both node_pool_defaults and node_pool_auto_config. This has not been resolved

Apply output:

│ Error: Provider produced inconsistent final plan
│ 
│ When expanding the plan for module.cluster.google_container_cluster.cluster to include new values learned so far during apply, provider
│ "registry.terraform.io/hashicorp/google-beta" produced an invalid new value for .node_pool_defaults: block count changed from 0 to 1.
│ 
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.
╵
╷
│ Error: Provider produced inconsistent final plan
│ 
│ When expanding the plan for module.cluster.google_container_cluster.cluster to include new values learned so far during apply, provider
│ "registry.terraform.io/hashicorp/google-beta" produced an invalid new value for .node_pool_auto_config: block count changed from 0 to 1.
│ 
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.

[hSATAC]

I am also having the same issue with 4.38.0