chore(deps): update k8s.io/kube-openapi digest to cdb1db5

[red-hat-konflux-kflux-prd-rh02]

This PR contains the following updates:

Package	Type	Update	Change
k8s.io/kube-openapi	indirect	digest	2dd684a → cdb1db5

---

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

---

To execute skipped test pipelines write comment /ok-to-test.

---

Documentation

Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.

[red-hat-konflux-kflux-prd-rh02]

ℹ️ Artifact update notice

File name: operator/go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

• 14 additional dependencies were updated
• The go directive was updated for compatibility reasons

Details:

Package	Change
go	1.23.0 -> 1.24.0
github.com/go-logr/logr	v1.4.1 -> v1.4.2
github.com/stretchr/testify	v1.8.4 -> v1.11.1
github.com/emicklei/go-restful/v3	v3.11.0 -> v3.13.0
github.com/go-openapi/jsonpointer	v0.19.6 -> v0.21.0
github.com/go-openapi/swag	v0.22.3 -> v0.25.4
github.com/google/gnostic-models	v0.6.8 -> v0.7.0
github.com/google/go-cmp	v0.6.0 -> v0.7.0
github.com/google/uuid	v1.3.0 -> v1.6.0
github.com/spf13/pflag	v1.0.5 -> v1.0.10
google.golang.org/protobuf	v1.33.0 -> v1.35.1
k8s.io/klog/v2	v2.110.1 -> v2.140.0
k8s.io/utils	v0.0.0-20230726121419-3b25d923346b -> v0.0.0-20260210185600-b8788abfbbc2
sigs.k8s.io/json	v0.0.0-20221116044647-bc3834ca7abd -> v0.0.0-20250730193827-2d320260d730
sigs.k8s.io/yaml	v1.4.0 -> v1.6.0

[openshift-ci]

Hi @red-hat-konflux-kflux-prd-rh02[bot]. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.