Use cases

• As a cluster administrator, I would like to create an Operator object that resolves to a plain bundle supported by Rukpak's plain provisioner, and see that the plain bundle contents are successfully installed
• As a cluster administrator, I would like to continue being able to install registry+v1 bundles via the Operator API
• As an operator developer, I would like to be able to ship static manifests for my operator and have no restrictions on the contents of my bundle (assuming valid Kubernetes YAML/JSON)

Assumptions

• A valid FBC catalog exists and contains one or more `olm.bundle` blobs that reference plain bundle images
• The `olm.bundle` blobs for plain bundle images include information that operator-controller can use to distinguish plain bundles from other bundles (e.g. a property that specifies the bundle format)

Out of Scope

• For this epic, there is no desire to define a plain bundle metadata format, or to build any tooling that simplifies the process of building catalogs that contain plain bundles. For now, it is expected that building a catalog that contains a plain bundle requires manual effort to construct a valid "olm.bundle" blob and include it in a catalog.