allow updating dataproc cluster autoscaling_policy

[danawillow]

Fixes hashicorp/terraform-provider-google#7096

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)

dataproc: fixed issues where updating `google_dataproc_cluster.cluster_config.autoscaling_policy` would do nothing, and where there was no way to remove a policy.

[modular-magician]

Hi! I'm the modular magician. Your PR generated some diffs in downstreams - here they are.

Diff report:

Terraform GA: Diff ( 4 files changed, 142 insertions(+), 8 deletions(-))
Terraform Beta: Diff ( 4 files changed, 142 insertions(+), 8 deletions(-))

[modular-magician]

I have triggered VCR tests based on this PR's diffs. See the results here: "https://ci-oss.hashicorp.engineering/viewQueued.html?itemId=145876"

[modular-magician]

I have triggered VCR tests in RECORDING mode for the following tests that failed during VCR: TestAccDataSourceComputeRegionSslCertificate|TestAccComputeSnapshot_encryptionCMEK|TestAccDataCatalogTag_dataCatalogEntryGroupTagExample|TestAccDataCatalogTag_dataCatalogEntryTagBasicExample|TestAccDataCatalogTag_update|TestAccDataprocCluster_withAutoscalingPolicy You can view the result here: "https://ci-oss.hashicorp.engineering/viewQueued.html?itemId=145881"

[c2thorn]

I suppose we don't need a check here because we are just making sure a diff doesn't exist after applying?

[danawillow]

Ideally we would have an import step, but we don't actually support import yet for dataproc clusters. I suppose it probably makes sense to check the object though to make sure removing the autoscaling policy actually removes it (vs just removing it from state). Will do shortly.

[modular-magician]

Hi! I'm the modular magician. Your PR generated some diffs in downstreams - here they are.

Diff report:

Terraform GA: Diff ( 4 files changed, 163 insertions(+), 8 deletions(-))
Terraform Beta: Diff ( 4 files changed, 163 insertions(+), 8 deletions(-))

[modular-magician]

I have triggered VCR tests based on this PR's diffs. See the results here: "https://ci-oss.hashicorp.engineering/viewQueued.html?itemId=146405"

[modular-magician]

I have triggered VCR tests in RECORDING mode for the following tests that failed during VCR: TestAccComputeSnapshot_encryptionCMEK|TestAccDataCatalogTag_dataCatalogEntryGroupTagExample|TestAccDataCatalogTag_dataCatalogEntryTagBasicExample|TestAccDataCatalogTag_update|TestAccDataprocCluster_withAutoscalingPolicy You can view the result here: "https://ci-oss.hashicorp.engineering/viewQueued.html?itemId=146407"

[danawillow]

Test passes, merging.