Change opm image from quay.io/operator-framework/upstream-opm-builder to quay.io/operator-framework/opm

[StopMotionCuber]

Description of the change: Bumping the opm image from quay.io/operator-framework/upstream-opm-builder to quay.io/operator-framework/opm

Motivation for the change: We are having issues with opm jobs, as we have a multi-arch cluster, where jobs are failing if ran on ARM64 nodes. The OLM seems to be using a deprecated opm image. See details in #2823 (comment)

Note: I don't completely know what I'm doing and whether the opm image is actually able to fully replace the upstream-opm-builder image. But I guess before digging down deeply into that rabbit hole, maintainers here should have a good understanding of that and evaluate that quicker than me.
Closes #2823

Architectural changes:

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]

Hi @StopMotionCuber. 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. 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.

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/test-infra repository.

[joelanford]

This file should not be directly changed. Instead, it seems we need OLM to bump its operator-registry version in go.mod and then re-vendor.

[StopMotionCuber]

Probably the re-vendoring would have done the same string replacement. Anyway, I force-pushed that change away, is the vendoring done automatically? I guess yes, as there is a "vendor" step in the workflows

[StopMotionCuber]

Wanted to check-in if there is something blocking this from being merged, as it has been 5 month now. This seems to be blocking ARM64 support, though it can be patched locally on the cluster by overriding the image

[perdasilva]

lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: perdasilva, StopMotionCuber

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 [perdasilva]

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

[perdasilva]

/lgtm

[StopMotionCuber]

Had to fix DCO, should be good now

[perdasilva]

/lgtm

[lukens]

Any idea when this might make it into a release?