operator-controller should not uninstall/rollback a failed install/upgrade

[joelanford]

Right now, operator-controller is using helm-operator-plugins, which automatically uninstalls failed installations and rolls back failed upgrades.

This is problematic because the installation or upgrade may have progressed to the point of no return. For example:

• a pre-install/pre-upgrade hook may have run a migration and a subsequent object failed to update.
• after any hooks run, a deployment may have started that ran a migration, but then subsequent objects fail to update.

In my opinion, a better behavior is to just stop, inform a user of the problem, and require human intervention to resolve and progress.

[joelanford]

I have a change in helm-operator-plugins that adds a knob to turn this behavior off. From a PoC standpoint, this looks very straightforward.

[joelanford]

PR up to make it possible for operator-controller to configure this behavior in helm-operator-plugins: operator-framework/helm-operator-plugins#348