Goal: Bootstrap the o/platform-operators repository, and massage the timflannagan/platform-operators repository downstream. Setup a CI pipeline using prow to get some signal, and vendor the o/operator-framework-rukpak repository.

Note(s):

• This is potentially blocked on the API review process for the top-level PlatformOperators API. In the meantime, this resource can be housed in the repository, and deployed after cluster creation during e2e runs.
• Introducing this repository to the OCP payload can be done in a follow-up ticket. Adding the CVP-required labels can be done in a follow-up ticket.
• Gating this repository when tech preview has been enabled can be done in a follow-up ticket.

AC:

• Create an OWNERS file
• Massage the timflannagan/platform-operators repository downstream
• Vendor the upstream rukpak project as a dependency.
• Add a root manifests directory for the PO manager and rukpak manifests
• Add the rukpak manager and webhook methods to the PO manager binary to ensure rukpak gets deployed with the PO stack.
• Create a Dockerfile that builds the PO manager binary, and copies the root manifests directory into /manifests and copies the rukpak manifests [1] in the container image.
• Contribute a ci-operator configuration to o/release and run sanity/e2e/unit/etc. checks as rehearsals prowjobs.

[1] https://github.com/operator-framework/operator-marketplace/blob/master/Dockerfile.rhel7#L12