Migrate deprecated gopkg.in/yaml.v3 to go.yaml.in/yaml/v3

[chimanjain]

Description of the change:
Migrate deprecated gopkg.in/yaml.v3 to go.yaml.in/yaml/v3
Reference: https://github.com/yaml/go-yaml

Motivation for the change:
The gopkg.in domain is deprecated and the yaml project has moved to go.yaml.in.
This ensures continued updates and security patches.

Testing remarks:

Reviewer Checklist

• Implementation matches the proposed design, or proposal is updated to match implementation
• Sufficient unit test coverage
• Sufficient end-to-end test coverage
• Bug fixes are accompanied by regression test(s)
• e2e tests and flake fixes are accompanied evidence of flake testing, e.g. executing the test 100(0) times
• tech debt/todo is accompanied by issue link(s) in comments in the surrounding code
• Tests are comprehensible, e.g. Ginkgo DSL is being used appropriately
• Docs updated or added to /doc
• Commit messages sensible and descriptive
• Tests marked as [FLAKE] are truly flaky and have an issue
• Code is properly formatted

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign dtfranz for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[openshift-ci]

Hi @chimanjain. Thanks for your PR.

I'm waiting for a operator-framework 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.

Tip

We noticed you've done this a few times! Consider joining the org to skip this step and gain /lgtm and other bot rights. We recommend asking approvers on your previous PRs to sponsor you.

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.

[Copilot]

Pull request overview

This PR updates Operator Lifecycle Manager (OLM) to use the newer go.yaml.in/yaml/v3 module path in place of the deprecated gopkg.in/yaml.v3, aligning local code with the YAML project’s domain migration.

Changes:

• Updated YAML v3 imports from gopkg.in/yaml.v3 to go.yaml.in/yaml/v3 in the cpb utility and a catalog operator test.
• Updated go.mod to add go.yaml.in/yaml/v3 v3.0.4 as a direct dependency and drop the direct gopkg.in/yaml.v3 requirement (though it remains indirect).

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
util/cpb/main.go	Switches YAML v3 import to the new go.yaml.in module path for bundle annotation parsing.
pkg/controller/operators/catalog/operator_test.go	Switches YAML v3 import to go.yaml.in and includes gofmt formatting-only adjustments in tests.
go.mod	Adds go.yaml.in/yaml/v3 as a direct requirement and adjusts YAML v3 dependency entries.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[chimanjain]

It is an indirect dependency which will be removedonce the direct dependencies migrate to the maintained yaml gomodule