Epic Goal

• When a new catalog comes out with a new version, the operator will automatically upgrade

Why is this important?

• The upgrade from 1.4.1 -> 1.5.0 was not tested
• The kataconfig schema changed, blocking the upgrade

Scenarios

1. OCP updates the redhat-operators catalog to have the new OSC
2. User has 1.4.1 installed and the catalog changes to a newer version
3. kataconfig with pp or kata workloads

Acceptance Criteria 

(The Epic is complete when...)

1. GA versions of each catalog is obviously tagged in the quay.io/openshift_sandboxed_containers/openshift-sandboxed-containers-operator-catalog repo.
   1. 1.4.1-GA
   2. 1.5.0-GA
   3. when 1.5.1 is GA, 1.5.1-GA
2. functions to install particular version of catalog
3. stories for other needed functions
4. function to set the starting catalog
5. functions to go through multiple versions (1.4.1 -> 1.5.0 - 1.5.1)
6. Should the automation be able to uninstall operators?
   1. 1.4.1 -> 1.5.0 puts it in Pending.  The fix is to unsubscribe, delete csv, resub to the 1.5.0/1.5.1

Additional context: