Given the operands are going to cache the ClusterPodPlacementConfig, we don't need the operator to re-deploy the operand when the log verbosity change.

The log verbosity can be a default one, and then the operands themselves can update it when their informer (MULTIARCH-5056) detects an update to the ClusterPodPlacementConfig.