Implement a fine-grained FSM and use the deploymentcontroller to control Pod Placement controllers

[aleskandro]

See #21 (comment)

Currently, we manage the deployments as children of the PodPlacementConfig in the PodPlacementConfig controller (that 'owns' Deployments, Services and MutatingWebhookConfigurations). Should we use a dedicated deploymentcontroller like https://github.com/openshift/library-go/blob/master/pkg/operator/deploymentcontroller/deployment_controller.go? It could help defining a more fine-grained control logic, and a dedicated FSM to support the ordered uninstallation issue too.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale