Split up the uninstall action on the operator bundle into two actions

[carolynvs]

The uninstall action currently tries to clean up all data created by the bundle/operator. Depending on the state of things, this can cause the action to hang. It could also cause a ton of trouble if people didn't actually want their bundles uninstalled.

Let's split up the bundle into two actions:

1. uninstall that only removes the operator, not data
2. one that removes existing data but does not trigger uninstall (i.e. we remove finalizers and delete like we do in our build scripts). Useful for local dev/test and when things have gone sideways.

• one that attempts to uninstall everything (to clean up resources). This may still hang or not be successful. So we want to delete as much as we can then report what is still lingering.