Add a --no-proxy option for the VCH

[hickeng]

Story
As a viadmin with a proxy that does not allow hairpin traffic I need to be able to exclude certain traffic from being proxied.

Detail
The ability to defining an exclusion set for connections that should not be proxied is desirable in general and an absolute requirement in some networking configurations.

This issue is for adding a basic no-proxy exclusion set to complement the current https and http proxy settings. As part of this issue, the types and origins of traffic for which this configuration is used should be documented (e.g. does traffic on the management network honor the proxy config?).

This issue is not expected to allow for per-network proxy configuration - that should be deferred until a manifest specification for a VCH is supported as adding more CLI options for niche/rare cases will only add to existing issues with complexity impacting ease-of-use.

This issue needs further refinement:

• design - which components should make use of the proxy settings and for which connections
• documentation - need to be explicit in the docs as to which connections will be proxied - include updates to network diagram with colouration to indicate connections that can/will be proxied.
• declaration of acceptance tests

bug2157829

[hickeng]

Added into 1.4.2 due to bug2157829 and explicit impediment in real usage.

[wjun]

The proxy settings are used by personality server and vicadmin process on VCH VM as the environment variables.