OCPBUGS-38927: Update Go version, API version and vendored libs to the same versions as in the openshift/api.

[metlos]

Cherry-pick of #561 to release-4.17.

[openshift-ci-robot]

@metlos: This pull request references Jira Issue OCPBUGS-38927, which is invalid:

• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required"

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to [this](https://github.com/openshift/cluster-samples-operator/pull/564): >Cherry-pick of #561 to release-4.17. Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fcluster-samples-operator). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.

[metlos]

/jira refresh

[openshift-ci-robot]

@metlos: This pull request references Jira Issue OCPBUGS-38927, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug

* bug is open, matching expected state (open) * bug target version (4.17.0) matches configured target version for branch (4.17.0) * bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST) * release note text is set and does not match the template * dependent bug [Jira Issue OCPBUGS-38926](https://issues.redhat.com//browse/OCPBUGS-38926) is in the state ON_QA, which is one of the valid states (MODIFIED, ON_QA, VERIFIED) * dependent [Jira Issue OCPBUGS-38926](https://issues.redhat.com//browse/OCPBUGS-38926) targets the "4.18.0" version, which is one of the valid target versions: 4.18.0 * bug has dependents

Requesting review from QA contact: /cc @jitendar-singh

In response to [this](https://github.com/openshift/cluster-samples-operator/pull/564#issuecomment-2312295744): >/jira refresh Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fcluster-samples-operator). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.

[metlos]

/retest

[openshift-ci[bot]]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: metlos, mfrancisc

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

The pull request process is described here

Needs approval from an approver in each of these files: - ~~[OWNERS](https://github.com/openshift/cluster-samples-operator/blob/release-4.17/OWNERS)~~ [metlos,mfrancisc] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment

[openshift-ci[bot]]

@metlos: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).

[metlos]

/label backport-risk-assessed /label cherry-pick-approved

[openshift-ci[bot]]

@metlos: Can not set label backport-risk-assessed: Must be member in one of these teams: [openshift-staff-engineers]

In response to [this](https://github.com/openshift/cluster-samples-operator/pull/564#issuecomment-2312613810): >/label backport-risk-assessed >/label cherry-pick-approved Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.

[openshift-ci[bot]]

@metlos: Can not set label cherry-pick-approved: Must be member in one of these teams: [openshift-staff-engineers]

In response to [this](https://github.com/openshift/cluster-samples-operator/pull/564#issuecomment-2312613810): >/label backport-risk-assessed >/label cherry-pick-approved Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.

[fbm3307]

/label backport-risk-assessed /label cherry-pick-approved

[openshift-ci-robot]

@metlos: Jira Issue OCPBUGS-38927: All pull requests linked via external trackers have merged:

• openshift/cluster-samples-operator#564

Jira Issue OCPBUGS-38927 has been moved to the MODIFIED state.

In response to [this](https://github.com/openshift/cluster-samples-operator/pull/564): >Cherry-pick of #561 to release-4.17. Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fcluster-samples-operator). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.

[openshift-bot]

[ART PR BUILD NOTIFIER]

Distgit: ose-cluster-samples-operator This PR has been included in build ose-cluster-samples-operator-container-v4.17.0-202408271906.p0.gd76dff9.assembly.stream.el9. All builds following this will include this PR.