Don't define no_proxy if proxy is not set

Related to #1948 (closed)

As described in the issue, when a baremetalhost is added or removed via a scale-up/down operation, the no_proxy value is automatically updated, causing "unwanted" rolling-upgrades. \ A very easy-to-handle case is when no http/https proxy are defined, in which case it doesn't seem necessary to define a `no_proxy.

Sorry for the ugly diff, I just added this line {{- if (or ($envAll.Values.http_proxy) ($envAll.Values.https_proxy)) -}} then re-indented the code.