[WIP]Manager Service Mesh Configuration in the Helm Chart

[iNoahNothing]

Description

This PR creates new values for creating and managing the extra config needed to integrate with Istio and Consul Connect service meshes to the chart.

Previously, the Consul Connector needed to be managed separately and the Istio sidecar injection needed to be done with a combination of different values. This PR makes it so Helm can automatically manage these resources.

Testing

A few sentences describing what testing you've done, e.g., manual tests, automated tests, deployed in production, etc.

Tasks That Must Be Done

• Did you update CHANGELOG.md?
  • Is this a new feature?
  • Are there any non-backward-compatible changes?
  • Did the envoy version change?
  • Are there any deprecations?
  • Will the changes impact how ambassador performs at scale?
    • Might an existing production deployment need to change:
      • memory limits?
      • cpu limits?
      • replica counts?
    • Does the change impact data-plane latency/scalability?
• Is your change adequately tested?
  • Was their sufficient test coverage for the area changed?
  • Do the existing tests capture the requirements for the area changed?
  • Is the bulk of your code covered by unit tests?
  • Does at least one end-to-end test cover the integration points your change depends on?
• Did you update documentation?
• Were there any special dev tricks you had to use to work on this code efficiently?
  • Did you add them to DEVELOPING.md?
• Is this a build change?
  • If so, did you test on both Mac and Linux?

[iNoahNothing]

I should probably write tests for this since there is actually a lot going on here 😞