Fix: Include user_service_account_mapping in Dataproc update mask

[anjalimalik]

Updated the resourceDataprocClusterUpdate function to explicitly include user_service_account_mapping in the update mask. This ensures that changes to the identity config are correctly detected and propagated to the Dataproc API during a Terraform apply.

dataproc: fixed an issue where changes to `user_service_account_mapping` in the `google_dataproc_cluster` resource were not propagated during updates.

[github-actions]

Googlers: For automatic test runs see go/terraform-auto-test-runs.

@c2thorn, a repository maintainer, has been assigned to review your changes. If you have not received review feedback within 2 business days, please leave a comment on this PR asking them to take a look.

You can help make sure that review is quick by doing a self-review and by running impacted tests locally.

[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.

google provider: Diff ( 1 file changed, 11 insertions(+))
google-beta provider: Diff ( 1 file changed, 11 insertions(+))

[modular-magician]

Tests analytics

Total tests: 83
Passed tests: 76
Skipped tests: 6
Affected tests: 1

Click here to see the affected service packages

• dataproc

Action taken

Found 1 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests

• TestAccDataprocCluster_updateIdentityConfigUserMapping

Get to know how VCR tests work

[modular-magician]

🟢 Tests passed during RECORDING mode:
TestAccDataprocCluster_updateIdentityConfigUserMapping [Debug log]

🟢 No issues found for passed tests after REPLAYING rerun.

---

🟢 All tests passed!

View the build log or the debug log for each test