Be able to switch controller strategy dynamically

Due to the original design of the application we had never supported the possibility to move from one controller strategy (ie, Deployment) to another (ie, KnativeService). This would require the clean up of the deployment resources before creating deployment of the new controller strategy without involving the garbage collection trait. Without a dedicated cleanup, we would duplicate the deployment as it happened in #5874.

Start by examining how controller strategy changes are handled and reproduce the duplication described in #5874. Ensure resources from the previous strategy are cleaned up before the new strategy is created, without relying on the garbage collection trait; done means switching between Deployment and KnativeService does not leave duplicate deployments.

Written by the indexing model from the issue text.