charts/gateway redis support, ingress update, restart on config change

[Gazza7205]

Description of the change

• Updated image
  • Updated to Gateway 11.0.00_CR1
  • this will cause a restart if you are not overriding the default image
• Redis Integration
  • Redis Configuration options for the Gateway (future use)
  • Added Redis SubChart
• Ingress
  • Backend service is now more configurable allowing the management service to be exposed via ingress controller
  • this should only be done in environments where the ingress controller does not have a Public Address
  • ingress.rules[n]backend can be set to "management"
• Restart on config change
  • A new flag has been added to facilitate auto redeploy of Gateways when there is a config change
  • Applies to the default config map only
  • does not include config.cwp, config.listenPorts or the Gateway Secret
• MySQL subChart updated

Benefits

• Updated Gateway Image to 11.0.00_CR1
• Redis integration options
• Remove the need to use rollout restart when updating configmaps
• Route to the Management service via Ingress Controller

Drawbacks

• This update will cause a rolling restart of the Gateway Deployment (new image)

Checklist

• [X] Chart version bumped in Chart.yaml according to semver.
• [X] Variables are documented in the README.md
• [X] Title of the PR starts with chart name (e.g. [charts/gateway])
• [X] If the chart contains a values-production.yaml apart from values.yaml, ensure that you implement the changes in both files