Add Gemini Data Sharing With Google Setting Binding resource

[PerlMonker303]

Release Note Template for Downstream PRs (will be copied)

See Write release notes for guidance.

Add new resources for Gemini Admin Control

`google_gemini_data_sharing_with_google_setting_binding`

[github-actions]

Hello! I am a robot. Tests will require approval from a repository maintainer to run.

@NickElliot, 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.

[PerlMonker303]

Currently failing because it depends on Gemini Data Sharing With Google Setting. Will fix after PR is submitted #12905.

[github-actions]

@NickElliot This PR has been waiting for review for 3 weekdays. Please take a look! Use the label disable-review-reminders to disable these notifications.

[NickElliot]

pending dependent pr

[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 ( 2 files changed, 159 insertions(+))
google-beta provider: Diff ( 5 files changed, 851 insertions(+), 2 deletions(-))
terraform-google-conversion: Diff ( 1 file changed, 96 insertions(+))

Missing test report

Your PR includes resource fields which are not covered by any test.

Resource: google_gemini_data_sharing_with_google_setting_binding (0 total tests)
Please add an acceptance test which includes these fields. The test should include the following:

resource "google_gemini_data_sharing_with_google_setting_binding" "primary" {
  data_sharing_with_google_setting_id = # value needed
  labels                              = # value needed
  location                            = # value needed
  product                             = # value needed
  setting_binding_id                  = # value needed
  target                              = # value needed
}

[modular-magician]

Tests analytics

Total tests: 0
Passed tests: 0
Skipped tests: 0
Affected tests: 0

Click here to see the affected service packages

• gemini

#### Non-exercised tests

🔴 Tests were added that are skipped in VCR:

• TestAccGeminiDataSharingWithGoogleSettingBinding_geminiDataSharingWithGoogleSettingBindingBasicExample_update
  🔴 Errors occurred during REPLAYING mode. Please fix them to complete your PR.

View the build log

[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 ( 2 files changed, 159 insertions(+))
google-beta provider: Diff ( 5 files changed, 851 insertions(+), 2 deletions(-))
terraform-google-conversion: Diff ( 1 file changed, 96 insertions(+))

Missing test report

Your PR includes resource fields which are not covered by any test.

Resource: google_gemini_data_sharing_with_google_setting_binding (2 total tests)
Please add an acceptance test which includes these fields. The test should include the following:

resource "google_gemini_data_sharing_with_google_setting_binding" "primary" {
  labels = # value needed
}

[modular-magician]

Tests analytics

Total tests: 12
Passed tests: 11
Skipped tests: 0
Affected tests: 1

Click here to see the affected service packages

• gemini

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

• TestAccGeminiDataSharingWithGoogleSettingBinding_geminiDataSharingWithGoogleSettingBindingBasicExample_update

Get to know how VCR tests work

[modular-magician]

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

🔴 Errors occurred during RECORDING mode. Please fix them to complete your PR.

View the build log or the debug log for each test