Registry overrides are being propagated to some data plane components

When using the registry-overrides flag to override registries for control plane components, it seems like the current implementation prpagates the override to some data plane components. 

It seems that certain components like multus, dns, and ingress get values for their containers' images from env vars set in operators on the control plane (cno/dns operator/konnectivity), and hence also get the overridden registry propagated to them. 

    100%

    1.Input a registry override through the HyperShift Operator
    2.Check registry fields for components on data plane
    3.
    

Data plane components that get registry values from env vars set in dns-operator, ingress-operator, cluster-network-operator, and cluster-node-tuning-operator get overridden registries. 

overriden registries should not get propagated to data plane