Update module sigs.k8s.io/cluster-api to v1.9.2

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
sigs.k8s.io/cluster-api	v1.9.1 -> v1.9.2

Trigger E2E tests:

/run cluster-test-suites

---

Release Notes

kubernetes-sigs/cluster-api (sigs.k8s.io/cluster-api)

v1.9.2

Compare Source

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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 was generated by Mend Renovate. View the repository job log.

[tinkerers-ci]

Oh No! 😱 At least one test suite has failed during the AfterSuite cleanup stage and might have left around some resources on the MC!

Be sure to check the full results in Tekton Dashboard to see which test suite has failed and then run the following on the associated MC to list all leftover resources:

PIPELINE_RUN="pr-cluster-test-suites-577-cluster-test-suites5k9vl"

NAMES="$(kubectl api-resources --verbs list -o name | tr '\n' ,)"
kubectl get "${NAMES:0:${#NAMES}-1}" --show-kind --ignore-not-found -l cicd.giantswarm.io/pipelinerun=${PIPELINE_RUN} -A 2>/dev/null

[tinkerers-ci]

cluster-test-suites

Run name	pr-cluster-test-suites-577-cluster-test-suites5k9vl
Commit SHA	61ff5c6
Result	Failed ❌

📋 View full results in Tekton Dashboard

Rerun trigger:
/run cluster-test-suites

---

Tip

To only re-run the failed test suites you can provide a TARGET_SUITES parameter with your trigger that points to the directory path of the test suites to run, e.g. /run cluster-test-suites TARGET_SUITES=./providers/capa/standard to re-run the CAPA standard test suite. This supports multiple test suites with each path separated by a comma.