Add OLM dependency on CertManager to Bundle
Summary
Operator depends on presence of CertManager, but we only talk about it in documentation thus automation tools may miss that.
The dependencies of an Operator are listed in a dependencies.yaml file in the metadata/ folder of a bundle. This file is optional and currently only used to specify explicit Operator-version dependencies.
Dependency Resolution documentation ( OpenShift, OLM ) gives us two options:
olm.package
This type indicates a dependency for a specific Operator version. The dependency information must include the package name and the version of the package in semver format. For example, you can specify an exact version such as 0.5.2 or a range of versions such as >0.5.1.
olm.gvk
With this type, the author can specify a dependency with group/version/kind (GVK) information, similar to existing CRD and API-based usage in a CSV. This is a path to enable Operator authors to consolidate all dependencies, API or explicit versions, to be in the same place.
Utilizing olm.gvk
dependency we can list dependency on CertManager that will not force end-user to install OLM version of cert-manager (for example our CI uses Helm chart) yet will prevent automated tools (like upstream OperatorHub submission pipelines) to make intelligent decisions when running tests.