Change the OPP policies to adopt OperatorPolicy

[gparvin]

Deploying operators with OperatorPolicy has benefits that should be adopted to help customers get better visibility into the operator status automatically.

Refs:

• https://issues.redhat.com/browse/OCPQE-25041

[mprahl]

@gparvin I'd recommend setting the channels explicitly for best compatibility. We've encountered issues with autodetecting the channel if the cluster has multiple catalogs providing the same operator. This is because the OLM PackageManifest API round robins between them in some unknown way.

[gparvin]

@gparvin I'd recommend setting the channels explicitly for best compatibility. We've encountered issues with autodetecting the channel if the cluster has multiple catalogs providing the same operator. This is because the OLM PackageManifest API round robins between them in some unknown way.

@mprahl I took your recommendation for a couple operators, but the others don't have a channel name that I can reliably generate without having to manually track it. ODF and Quay had versions built in their channel names, example: stable-3.12.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: gparvin, mprahl

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 [gparvin,mprahl]

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