As an engineer in ACM, I want to be able to update HIVE to their latest more frequently.
A mechanism will be developed to update HIVE for every stream on a schedule to be determined.

The following concerns should be addressed:

• how to maintain sufficient for z-stream
• how to handle updates that require specific / additional testing
• what other components / teams need to be notified before/after the update

The mechanism must account for all of the following:

• When bumping hive, you must bump all the things: the container image ref, CRDs, RBAC, the hive-operator Deployment, etc. When these get out of sync, we have Problems™.
• When bumping hive, programmatic consumers of hive APIs (at least Assisted Installer. Others? Please make a complete list below.) must revendor to pick up CRD changes. When these get out of sync, we have Problems™.
• Server Foundation work example: https://issues.redhat.com/browse/ACM-26426
• Site Config work example: https://issues.redhat.com/browse/ACM-26432
• Assisted Installer work example: https://issues.redhat.com/browse/ACM-26433