Update module github.com/onsi/ginkgo/v2 to v2.22.2

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
github.com/onsi/ginkgo/v2	v2.22.1 -> v2.22.2

Trigger E2E tests:

/run cluster-test-suites

---

Release Notes

onsi/ginkgo (github.com/onsi/ginkgo/v2)

v2.22.2

Compare Source

What's Changed

• Bump golang.org/x/net from 0.32.0 to 0.33.0 by @​dependabot in https://github.com/onsi/ginkgo/pull/1496
• Bump golang.org/x/crypto from 0.17.0 to 0.31.0 in /ginkgo/performance/_fixtures/performance_fixture by @​dependabot in https://github.com/onsi/ginkgo/pull/1498
• Bump github.com/onsi/gomega from 1.36.1 to 1.36.2 by @​dependabot in https://github.com/onsi/ginkgo/pull/1499

Full Changelog: onsi/ginkgo@v2.22.1...v2.22.2

---

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-582-cluster-test-suiteszvmpx"

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-582-cluster-test-suiteszvmpx
Commit SHA	91a0857
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.