Pods missing Temporal schema volume mounts when using external GCP services (Airbyte Helm Chart 1.7.0)

### Helm Chart Version

Airbyte Helm Chart: 1.7.0 Temporal Version: 1.28.0

### What step the error happened?

On deploy

### Relevant information

Using Helm template rendering, deploying to GCP.
External resources:

PostgreSQL on GCP Cloud SQL
GCS Bucket configured for blob storage
GCP Secret Manager for secret injection

All GCP configurations are verified to be working (i.e., secrets are loaded, tables created successfully, storage accessed).

After deploying Airbyte and Temporal using Helm templates with external GCP-managed services, the Temporal pods fail to start due to an apparent missing volume mount. Specifically, the expected schema directories for Temporal are not present, which causes the update tasks to skip or fail to apply correctly.

Observed Volume Mounts:
In the pod spec, we only see:

```
Mounts:
/etc/temporal/config/dynamicconfig/ from airbyte-temporal-dynamicconfig (rw)
/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-kztgv (ro)
```

### Relevant log output

```shell
TEMPORAL_ADDRESS is not set, setting it to 1____:7233
PostgreSQL started. Setup PostgreSQL schema. 2025-07-18T21:46:11.382Z INFO Starting schema setup {"config": {"SchemaFilePath":"","SchemaName":"","InitialVersion":"0.0","Overwrite":false,"DisableVersioning":false}, "logging-
2025-07-18T21:46:11.385Z DEBUG Setting up version tables {"logging-call-at": "/home/runner/work/docker-builds/docker-builds/temporal/tools/common/schema/setuptask.go:50"}
2025-07-18T21:46:11.391Z DEBUG Current database schema version 1.17 is greater than initial schema version 0.0. Skip version upgrade {"logging-call-at": "/home/runner/work/docker2025-07-18T21:46:11.391Z INFO Schema setup complete {"logging-call-at": "/home/runner/work/docker-builds/docker-builds/temporal/tools/common/schema/setuptask.go:126"}
2025-07-18T21:46:11.434Z INFO UpdateSchemaTask started {"config": {"DBName":"","TargetVersion":"","SchemaDir":"/etc/temporal/schema/postgresql/v12/temporal/versioned","SchemaName 2025-07-18T21:46:11.439Z DEBUG Schema Dirs: [] {"logging-call-at": "/home/runner/work/docker-builds/docker-builds/temporal/tools/common/schema/updatetask.go:188"}
2025-07-18T21:46:11.439Z DEBUG found zero updates from current version 1.17 {"logging-call-at": "/home/runner/work/docker-builds/docker-builds/temporal/tools/common/schema/update
2025-07-18T21:46:11.439Z INFO UpdateSchemaTask done {"logging-call-at": "/home/runner/work/docker-builds/docker-builds/temporal/tools/common/schema/updatetask.go:103"}
2025-07-18T21:46:11.530Z INFO Starting schema setup {"config": {"SchemaFilePath":"","SchemaName":"","InitialVersion":"0.0","Overwrite":false,"DisableVersioning":false}, "logging-
2025-07-18T21:46:11.530Z DEBUG Setting up version tables {"logging-call-at": "/home/runner/work/docker-builds/docker-builds/temporal/tools/common/schema/setuptask.go:50"}
2025-07-18T21:46:11.535Z DEBUG Current database schema version 1.9 is greater than initial schema version 0.0. Skip version upgrade {"logging-call-at": "/home/runner/work/docker-
2025-07-18T21:46:11.536Z INFO Schema setup complete {"logging-call-at": "/home/runner/work/docker-builds/docker-builds/temporal/tools/common/schema/setuptask.go:126"}
2025-07-18T21:46:11.582Z INFO UpdateSchemaTask started {"config": {"DBName":"","TargetVersion":"","SchemaDir":"/etc/temporal/schema/postgresql/v12/visibility/versioned","SchemaNa
2025-07-18T21:46:11.587Z DEBUG Schema Dirs: [] {"logging-call-at": "/home/runner/work/docker-builds/docker-builds/temporal/tools/common/schema/updatetask.go:188"}
2025-07-18T21:46:11.587Z DEBUG found zero updates from current version 1.9 {"logging-call-at": "/home/runner/work/docker-builds/docker-builds/temporal/tools/common/schema/updatet
2025-07-18T21:46:11.587Z INFO UpdateSchemaTask done {"logging-call-at": "/home/runner/work/docker-builds/docker-builds/temporal/tools/common/schema/updatetask.go:103"}
Temporal CLI address: 172.28.2.202:7233.

time=2025-07-18T21:46:11.635 level=ERROR msg="failed reaching server: connection error: desc = \"transport: Error while dialing: dial tcp 172.28.2.202:7233: connect: connection refused\""
2025/07/18 21:46:11 Loading config; env=docker,zone=,configDir=config
2025/07/18 21:46:11 Loading config files=[config/docker.yaml]
Unable to load configuration: config file corrupted: yaml: line 11: did not find expected key.

Waiting for Temporal server to start...

stream closed EOF for airbyte/airbyte-temporal-5c7bbdcb55-pnrnq (airbyte-temporal)
```

Start by rendering the Airbyte Helm Chart 1.7.0 manifests and inspect the Temporal pod specifications and volume mounts. Compare them with the expected /etc/temporal/schema/postgresql/v12/temporal/versioned and visibility/versioned directories shown in the logs; done means the schema mounts are present and the Temporal pods start successfully with the external GCP services.

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