chore(deps): update registry.k8s.io/csi-vsphere/syncer docker tag to v3.7.1

[Varashi]

This PR contains the following updates:

Package	Update	Change
registry.k8s.io/csi-vsphere/syncer	patch	v3.7.0 → v3.7.1

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate.

[coderabbitai]

📝 Walkthrough

Walkthrough

The vSphere CSI driver controller Deployment receives a patch version bump for the syncer container image, updating the tag from v3.7.0 to v3.7.1 in the Kubernetes manifest.

Changes

vSphere CSI Driver Update

Layer / File(s)	Summary
vSphere syncer image patch update cluster-talos/kubernetes/infrastructure/core/vsphere-csi/app/vsphere-csi-driver.yaml	The vsphere-syncer container image tag is updated from registry.k8s.io/csi-vsphere/syncer:v3.7.0 to registry.k8s.io/csi-vsphere/syncer:v3.7.1 in the controller Deployment.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A syncer hops from v3.7.0 so fine,
To v3.7.1, a patch in line,
One tiny change, so clean and bright,
The vSphere CSI takes its flight! ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: updating the vsphere-syncer container image tag from v3.7.0 to v3.7.1, which is the only modification in the changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch renovate/registry.k8s.io-csi-vsphere-syncer-3.x

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

kustomization diff:

--- cluster-talos/kubernetes/infrastructure/core/vsphere-csi/app Kustomization: flux-system/vsphere-csi Deployment: vmware-system-csi/vsphere-csi-controller

+++ cluster-talos/kubernetes/infrastructure/core/vsphere-csi/app Kustomization: flux-system/vsphere-csi Deployment: vmware-system-csi/vsphere-csi-controller

@@ -165,13 +165,13 @@

         - name: INCLUSTER_CLIENT_BURST
           value: '100'
         - name: CSI_NAMESPACE
           valueFrom:
             fieldRef:
               fieldPath: metadata.namespace
-        image: registry.k8s.io/csi-vsphere/syncer:v3.7.0
+        image: registry.k8s.io/csi-vsphere/syncer:v3.7.1
         imagePullPolicy: Always
         name: vsphere-syncer
         ports:
         - containerPort: 2113
           name: prometheus
           protocol: TCP