RollingUpgrade are wrongly triggered during scale down/up operations

During scale-up/scale-down operations, it was detected that rolling-upgrades were triggered following the deletion/addition of BMHs in the values (once the scaling operation had been performed). Deleting BMHs should not trigger rolling-upgrades. \

After a quick investigation, it seems that this behavior is triggered by the addition or the deletion of BMH IPs in the no_proxy value.
The no_proxy value is then propagated to the cluster Helm release, which is then included in the rke2ControlPlane/rke2configTemplate (same for kubeadm).