OLM cleans up Operator workloads

Goal: OLM should provide the option to clean up Operator workload, that would otherwise become orphaned.

Benefit hypothesis: Operator users have a reliable way to cleanly remove resources that have been created on their behalf.

Why is this important: Today OLM when uninstalling an Operator its CRDs are left intact. That means that workloads are not deleted. Without the Operator around to process deletion events of custom resources it may become hard to cleanly remove deployed resources, especially when it's resource that are outside of the cluster. This is especially important during deletion of the whole cluster it is desired to remove all off-cluster managed resource before the cluster is destroyed.

Acceptance criteria:

• OLM can delete Operands upon Operator removal
• OLM cleans up Operands upon Cluster destruction