CMP-4370,CMP-4402,CMP-4405: Bump Go to 1.25.11 and update dependencies [release-1.9]

[abushkin-redhat]

What

Bump Go toolchain from 1.25.8 to 1.25.11 and refresh vendored dependencies
to their latest Go 1.25-compatible patch releases; re-vendored.

Why

Pick up Go standard-library security fixes flagged against the
compliance-operator-bundle image (Red Hat ProdSec trackers):

CVE	Jira	Go package
CVE-2026-33811	CMP-4370	net
CVE-2026-27145	CMP-4402	crypto/x509
CVE-2026-42504	CMP-4405	mime

Changes

Package	From	To
go (toolchain)	1.25.8	1.25.11
golang.org/x/crypto	v0.52.0	v0.54.0
golang.org/x/net	v0.55.0	v0.57.0
golang.org/x/sys	v0.45.0	v0.47.0
golang.org/x/text	v0.37.0	v0.40.0
golang.org/x/term	v0.43.0	v0.45.0
golang.org/x/mod	v0.36.0	v0.38.0
golang.org/x/tools	v0.45.0	v0.48.0
golang.org/x/sync	v0.20.0	v0.22.0
golang.org/x/exp	Jun 3	Jul 27
k8s.io/*	v0.35.5	v0.35.7
k8s.io/kube-openapi	Jun 3	Jul 21
k8s.io/utils	May 7	Jul 7
sigs.k8s.io/structured-merge-diff/v6	v6.3.2	v6.4.2
google.golang.org/genproto	Jun 8	Aug 3
google.golang.org/protobuf	v1.36.11	v1.36.12-pre
go.opentelemetry.io/otel	v1.43.0	v1.45.0
github.com/google/cel-go	v0.26.1	v0.30.0
github.com/go-logr/logr	v1.4.3	v1.4.4
go-openapi/jsonpointer	v0.23.1	v1.0.0
go-openapi/jsonreference	v0.21.6	v1.0.0
go-openapi/swag	v0.25.5	v0.27.1

All updated dependencies require only go 1.25.0 — verified via each
module's go.mod. Packages whose latest versions require go >= 1.26.0
(e.g., sigs.k8s.io/controller-runtime@v0.24.1,
github.com/openshift/library-go@latest) were left at their current versions.

Verification

• go mod tidy produces no diff
• go mod vendor produces no diff
• go build ./... compiles cleanly
• CI pipelines pass

[openshift-ci-robot]

@abushkin-redhat: This pull request references CMP-4370 which is a valid jira issue.

This pull request references CMP-4402 which is a valid jira issue.

This pull request references CMP-4405 which is a valid jira issue.

Details

In response to this:

What

Bump Go toolchain from 1.25.8 to 1.25.11 and refresh vendored dependencies
to their latest Go 1.25-compatible patch releases; re-vendored.

Why

Pick up Go standard-library security fixes flagged against the
compliance-operator-bundle image (Red Hat ProdSec trackers):

CVE	Jira	Go package
CVE-2026-33811	CMP-4370	net
CVE-2026-27145	CMP-4402	crypto/x509
CVE-2026-42504	CMP-4405	mime

Changes

Package	From	To
go (toolchain)	1.25.8	1.25.11
golang.org/x/crypto	v0.52.0	v0.54.0
golang.org/x/net	v0.55.0	v0.57.0
golang.org/x/sys	v0.45.0	v0.47.0
golang.org/x/text	v0.37.0	v0.40.0
golang.org/x/term	v0.43.0	v0.45.0
golang.org/x/mod	v0.36.0	v0.38.0
golang.org/x/tools	v0.45.0	v0.48.0
golang.org/x/sync	v0.20.0	v0.22.0
golang.org/x/exp	Jun 3	Jul 27
k8s.io/*	v0.35.5	v0.35.7
k8s.io/kube-openapi	Jun 3	Jul 21
k8s.io/utils	May 7	Jul 7
sigs.k8s.io/structured-merge-diff/v6	v6.3.2	v6.4.2
google.golang.org/genproto	Jun 8	Aug 3
google.golang.org/protobuf	v1.36.11	v1.36.12-pre
go.opentelemetry.io/otel	v1.43.0	v1.45.0
github.com/google/cel-go	v0.26.1	v0.30.0
github.com/go-logr/logr	v1.4.3	v1.4.4
go-openapi/jsonpointer	v0.23.1	v1.0.0
go-openapi/jsonreference	v0.21.6	v1.0.0
go-openapi/swag	v0.25.5	v0.27.1

All updated dependencies require only go 1.25.0 — verified via each
module's go.mod. Packages whose latest versions require go >= 1.26.0
(e.g., sigs.k8s.io/controller-runtime@v0.24.1,
github.com/openshift/library-go@latest) were left at their current versions.

Verification

• go mod tidy produces no diff
• go mod vendor produces no diff
• go build ./... compiles cleanly
• CI pipelines pass

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 openshift-eng/jira-lifecycle-plugin repository.

[yuumasato]

Needs the same pin on 1.25.11 that the PR for master has.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abushkin-redhat, taimurhafeez

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [taimurhafeez]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[taimurhafeez]

/lgtm