Read PROXY env in more places when deploying

[divolgin]

What this PR does / why we need it:

When running automated install, PROXY env variables not used.

divolgin@dmitriy-kots-001:~$ export HTTP_PROXY=http://10.128.0.23:3128
divolgin@dmitriy-kots-001:~$ export HTTPS_PROXY=http://10.128.0.23:3128
divolgin@dmitriy-kots-001:~$ export NO_PROXY=.cluster.local,10.0.0.0/8,10.96.0.1,35.225.92.50,kotsadm-rqlite,kotsadm-postgres,kotsadm-minio,kotsadm-api-node
divolgin@dmitriy-kots-001:~$ ./kots install dmitriykots2/beta --copy-proxy-env=true --license-file dmitriy-kots-3-new\ \(2\).yaml --config-values config.yaml --shared-password password --namespace dmitriykots2 --skip-preflights 
  • Checking for license update ✓  
  • Deploying Admin Console
    • Creating namespace ✓  
    • Waiting for datastore to be ready ✓  
  • Waiting for Admin Console to be ready ✓  
  • Waiting for installation to complete ✓  

$ kubectl -n dmitriykots2 describe deployment replicated | grep Environment -A 10
    Environment:
      HTTP_PROXY:                    http://10.128.0.23:3128
      HTTPS_PROXY:                   http://10.128.0.23:3128
      NO_PROXY:                      .cluster.local,10.0.0.0/8,10.96.0.1,35.225.92.50,kotsadm-rqlite,kotsadm-postgres,kotsadm-minio,kotsadm-api-node,kotsadm-rqlite,kotsadm-postgres,kotsadm-minio,kotsadm-api-node
      REPLICATED_NAMESPACE:           (v1:metadata.namespace)
      REPLICATED_POD_NAME:            (v1:metadata.name)
      DISABLE_OUTBOUND_CONNECTIONS:  false
      IS_HELM_MANAGED:               true
      HELM_RELEASE_NAME:             replicated
      HELM_RELEASE_NAMESPACE:        dmitriykots2
      HELM_PARENT_CHART_URL:         

Which issue(s) this PR fixes:

https://app.shortcut.com/replicated/story/111175/support-for-installing-behind-a-proxy#activity-112112

Does this PR require a test?

Does this PR require a release note?

Fixes an issue where the values provided to the --http-proxy, --https-proxy, and --no-proxy flags for the kots install command were not propagated to the Replicated SDK when running an automated install.

Does this PR require documentation?