Modify clusters-app-operator to fix vSphere proxy behaviour

[vxav]

Current setup
When a vSphere WC is deployed, cluster app operator (CAO) applies the HTTP proxy configuration from the MC to the WC by mutating the cluster values secret that gets applied to all the apps and cluster.

Problem
For our current CAPV on AWS testing, it fails because goat uses a proxy which gets propagated to the WC which breaks it.

Solution
Change CAO so it will respect proxy.enabled=false in the cluster chart values.

[anvddriesch]

Deploying the PR giantswarm/cluster-apps-operator#530 to goat solves the problem of proxy env injection

[anvddriesch]

I just released the patch for CAO