Support OLMv1 API for getting Operator's installed namespaces

[razo7]

Why we need this PR

• Support OLMv1 API for getting Operator's installed namespaces
• Include suggested namespace by default when gathering Medik8s operators
• Gather namespaces from ClusterExtension (OLM v1) without overwriting subscription results

Changes made

• Include OLM Operator's installed namespaces with OLM v1 API and append them to OLM v0 list
• All of Medik8s operators CSV include a operatorframework.io/suggested-namespace annotation with a value of openshift-workload-availability
• Append namespaces from ClusterExtension to the list of installed medik8s namespaces

Which issue(s) this PR fixes

RHWA-448

Test plan

[slintes]

Did you test this on older clusters where the ClusterExtension CRD doesn't exist yet? 🤔
Will be relevant later on as well, when Subscription doesn't exist anymore on newer clusters.

[razo7]

Did you test this on older clusters where the ClusterExtension CRD doesn't exist yet? 🤔
Will be relevant later on as well, when Subscription doesn't exist anymore on newer clusters.

• I tested it (quay.io/oraz/must-gather:pr-23-1) on OCP 4.17 where the OLM v1 API is missing.

➜  oc get ClusterExtension
error: the server doesn't have a resource type "ClusterExtension"
➜  oc get ClusterCatalog
error: the server doesn't have a resource type "ClusterCatalog"

IIRC, OLM v1 API is TP since 4.18.

• On OCP 4.21, where both of the APIs exist, it works and looks for the namespaces of the installed operators.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: razo7, slintes

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 [razo7,slintes]

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