WHY
We need to implement a smooth transition from OO to OBO that results in no down time during upgrades for existing installations of RHOAM.

WHAT
When an existing RHOAM installation is upgraded from N to N+1 (where N+1 is the first release containing the OBO feature branch), we need to uninstall and cleanup the OO components, ideally in a non-service affecting way.

HOW
We should be able to keep the reconciler with just the finalizer in it and then mark the stage for uninstall. The finalizer and any other remaining bits of code needed for the uninstallation will be removed when upgrading from N+1 to N+2.

TESTS
<List of related tests>

DONE

• OO is uninstalled when RHOAM is upgraded from N to N+1
• The upgrade is non-service affecting if possible
• Verify that the OO namespace is removed - may require update to addon.yaml