WHY
Knowing how the package-operator is installed, released, and versioned will give us a better understanding of it's capabilities and help us ensure RHOAM installations' stability.

WHAT
There are a number of unknowns related to how the package-operator is installed, versioned, and released that we would like to clear up before we release OBO support. Specifically we would like to determine the following:

1. How is the package-operator installed on OSD clusters? It seems like the package-operator is installed by the package-operator in the form of a ClusterPackage CR which on the surface seems like a circular dependency.
2. Is the package-operator version the same on stage and production clusters? Is their a lag in the versions after a new release?
3. Is there an existing mechanism for users of the package-operator to get advanced warning before significant/breaking changes are released?

Ideally the outcome of this Spike would be a doc answering these questions. This doc can be put in the feature's folder on the team drive here.

HOW
The package-operator docs can be found here. The package-operator team can be reached using `@package-operator` on the `#forum-managed-tenants` Slack channel.

TESTS
<List of related tests>

DONE

• Determined how package-operator is installed
• Determined if there is a discrepancy/lag in versioning on stage vs production clusters
• Determined if there is an existing mechanism for users of the package-operator to get advanced warning before significant/breaking changes are released