If DevWorkspace (WebTerminal instance) is idled after Operator is uninstalled:

• web-terminal-exec will update DevWorkspace CR to trigger stop (spec.started: false)
• BUT since Controller is responsible for reflecting DevWorkspace spec to k8s cluster objects and it's already removed - Deployment never will be scaled to zero

I don't a good idea what we can do with that on OLM or controller side...

What we could try to do:
1. Write documentation for administrators that after uninstalling WebTerminal Operator, DevWorkspace CRs and related k8s objects may still be on the cluster and them must clean up them manually (I suppose dedicated admin should be able to do it, I can check);
^ there is no place yet where we can put that doc

2. Or we could try to process STOP action by the secondary controller that is deployed in a separate deployment that won't be cleaned up by OLM.
But then kube:admin is supposed to clean up that deployment manually after they make sure all DevWorkspace CRs are idled or even removed. Dedicated admin does not have such permissions (delete deployment in openshift-operators namespace);

^ seems to be really tricky way to go. I would prefer to go simpler #1