[CONTP-1803] Migrate CSI registrar image to registry.k8s.io

[tbavelier]

What changed

Updates the datadog-csi-driver chart for the CSI registrar registry migration:

• Bumps datadog-csi-driver from 0.15.0 to patch version 0.15.1
• Changes the default registrar.image.repository from k8s.gcr.io/sig-storage/csi-node-driver-registrar to registry.k8s.io/sig-storage/csi-node-driver-registrar
• Updates the GKE Autopilot DaemonSet matching label to datadog-datadog-csi-driver-daemonset-exemption-v1.1.1
• Keeps the existing v1.1.0 WorkloadAllowlist path in the AllowlistSynchronizer and adds v1.1.1, so the previous version remains synced until the new one is confirmed available across GKE node versions
• Adds a CSI AllowlistSynchronizer baseline fixture and updates CSI rendered baselines

Associated WorkloadAllowlist PR: https://github.com/DataDog/datadog-gke-workload-allowlist/pull/19

Why

k8s.gcr.io is frozen and Kubernetes images have moved to registry.k8s.io. The CSI chart default image and the GKE Autopilot WorkloadAllowlist label need to move together so Autopilot workloads match the new allowlist version.

QA instructions

1. Deploy the WorkloadAllowlist from the associated PR into a GKE Autopilot test cluster
2. Install the CSI chart on a GKE Autopilot cluster with WorkloadAllowlist support, using default CSI chart values.
3. Confirm the rendered DaemonSet has cloud.google.com/matching-allowlist: datadog-datadog-csi-driver-daemonset-exemption-v1.1.1.
4. Confirm the rendered registrar image is registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.0.1.
5. Confirm the AllowlistSynchronizer includes both v1.1.0 and v1.1.1 allowlist paths.
6. Confirm the CSI DaemonSet is admitted by GKE Warden and pods become Ready.

Validation

Tested on my GKE autopilot cluster v1.36.0-gke.3712000

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f23001474e

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".