feat: allow user-specified connection ID in BigQueryConnection Connection

[jingyih]

Allow user to specify connection ID in BigQueryConnectionConnection via spec.ResourceID field.

// Immutable. Optional.
// The BigQuery Connection ID used for resource creation or acquisition.
// For creation: If specified, this value is used as the connection ID. If not provided, a UUID is generated and stored in the `status.ExternalRef` field.
// For acquisition: This field must be provided to identify the connection resource to acquire.
ResourceID *string `json:"resourceID,omitempty"`

Fixes #3140

[jingyih]

/assign @yuwenma

[yuwenma]

/lgtm
/approve
/hold

Looks great. a few nits ( I think we want to fix the immutable check)
But feel free to unhold and do it in follow-up PRs

[yuwenma]

/lgtm
/approve

[google-oss-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: yuwenma

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [yuwenma]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[yuwenma]

/hold cancel

[jingyih]

We could merge this manually if this is blocking the release. Sample test is flaky. First run failed with

2024-11-12T20:20:25.1143716Z         --- FAIL: TestAllInSeries/samples/workerpool-with-peered-network (240.79s)

Second run failed with

2024-11-12T21:33:03.1181469Z         --- FAIL: TestAllInSeries/samples/bigquerydatatransferconfig-scheduledquery (181.73s)

I just triggered a 3rd run.