A workload container (connector-sidecar) doesn’t have extraInitContainers section - it can't connect to Google Cloud SQL on GKE

### Helm Chart Version

2.0.19

### What step the error happened?

Other

### Relevant information

I’m trying to launch Airbyte on GKE with an external database on Google Cloud. I need to run Cloud SQL Auth Proxy (`cloud-sql-proxy`) in a sidecar pattern, so I have to specify a configuration in `extraInitContainers` for all services. Services like cron, sever, worker, temporal, etc - work fine, I can access the UI and sign in.

Once I try to add a source, Airbyte launches the new Pod `urce-hubspot-check...` to verify the connection, but the Pod doesn’t have access to the database: `Failed to obtain JDBC Connection`. Inspecting logs shows that there is no `cloud-sql-proxy`, also, if I check Yaml for the Pod - there is only `airbyte/workload-init-container` in the `initContainer` section.

Is it possible to specify extraInitContainers for the workload?

Thank you!

### Relevant log output

```shell

```

Start by tracing the Helm chart templates that create workload pods, then compare their init-container configuration with the cron, server, worker, and temporal services described in the issue. Verify how extraInitContainers is passed to the connector-sidecar workload; done means configured workload pods include the Cloud SQL Auth Proxy and can verify a source connection.

由索引模型根據 Issue 內容生成。