feat(make): Introduce olm-deploy goal, a one-shot OLM deployer

[olivergondza]

What type of PR is this?

Uncomment only one /kind line, and delete the rest.
For example, > /kind bug would simply become: /kind bug

/kind bug
/kind cleanup
/kind failing-test

/kind enhancement

/kind documentation
/kind code-refactoring

What does this PR do / why we need it:

Implements https://github.com/redhat-developer/gitops-operator/?tab=readme-ov-file#making-the-operator-available-on-the-in-cluster-operatorhub and https://github.com/redhat-developer/gitops-operator/?tab=readme-ov-file#re-build-and-deploy. Including waiting for operator to be up, and essential error reporting.

This builds and deploys new image/bundle/catalog, deploys it and waits for operator pod running. It is not needed to visit UI at all.

Have you updated the necessary documentation?

• Documentation update is required by this PR.
• [no] Documentation has been updated.

Which issue(s) this PR fixes:

None

Test acceptance criteria:

• [n/a] Unit Test
• [n/a] E2E Test

How to test changes / Special notes to the reviewer:

[olivergondza]

No changes related to the prod code, tests or their execution. Tests failures are unrelated.

[olivergondza]

@jgwest, can you please take a look?

[olivergondza]

@jgwest, @svghadi, please take a look if this is something we want in. (Asking before working on resolving conflicts)

[jgwest]

Rebased and added a comment to shell script.

[jgwest]

Works great, LGTM, thanks @olivergondza!

[jgwest]

/approve
/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jgwest

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

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

[jgwest]

Cluster init fail
/retest

[olivergondza]

@jgwest, Thanks for taking a look. Just pointing out that this make goal not utilized by CI, so whatever test results will be irrelevant to the changes reviewed. Can we only merge when tests are green?

[openshift-ci]

@olivergondza: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/v4.14-kuttl-sequential	a23cefb	link	false	/test v4.14-kuttl-sequential

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.