[release/4][BACKPORT] [auto-bump][chart] ambassador-6.7.13

[d2iq-mergebot]

This is a backport of the following PR:

#1255

Add Release Notes or "None":

[1.13.10]
- Bugfix: Fixed a regression when specifying a comma separated string for `cors.origins` on the
  `Mapping` resource. ([#3609])
- Change: Envoy-configuration snapshots get saved (as `ambex-#.json`) in `/ambassador/snapshots`.
  The number of snapshots is controlled by the `AMBASSADOR_AMBEX_SNAPSHOT_COUNT` environment
  variable; set it to 0 to disable. The default is 30.
- Change: Set `AMBASSADOR_AMBEX_NO_RATELIMIT` to `true` to completely disable ratelimiting Envoy
  reconfiguration under memory pressure. This can help performance with the endpoint or Consul
  resolvers, but could make OOMkills more likely with large configurations. The default is `false`,
  meaning that the rate limiter is active.
- Bugfix: The `Mapping` resource can now specify `docs.timeout_ms` to set the timeout when the 
  Dev Portal is fetching API specifications.
- Bugfix: The Dev Portal will now strip HTML tags when displaying search results, showing just
  the actual content of the search result.
- Change: Consul certificate-rotation logging now includes the fingerprints and validity
  timestamps of certificates being rotated.

[1.13.8]
- Bugfix: Ambassador Agent now accurately reports up-to-date Endpoint information to Ambassador Cloud
- Feature: Ambassador Agent reports ConfigMaps and Deployments to Ambassador Cloud to provide a better Argo Rollouts experience. See [Argo+Ambassador documentation](https://www.getambassador.io/docs/argo) for more info.

[1.13.7]
- Feature: Add AMBASSADOR_JSON_LOGGING to enable JSON for most of the Ambassador control plane. Some (but few) logs from gunicorn and the Kubernetes client-go package still log text.
- Bugfix: Fixed a bug where the Consul resolver would not actually use Consul endpoints with TCPMappings.
- Change: Ambassador now calculates its own memory usage in a way that is more similar to how the kernel OOMKiller tracks memory.

[1.13.6]
- Bugfix: Fixed a regression where Ambassador snapshot data was logged at the INFO label when using AMBASSADOR_LEGACY_MODE=true

[1.13.5]
- Bugfix: Fix a regression from 1.8.0 that prevented Ambassador module config keys `proper_case` and `preserve_external_request_id` from working correctly.
- Bugfix: Fixed a regression in detecting the Ambassador Kubernetes service that could cause the wrong IP or hostname to be used in Ingress statuses (thanks, [Noah Fontes](https://github.com/impl)!

[1.13.4]
- Bugfix: Incorporate the Envoy 1.15.5 security update by adding the `reject_requests_with_escaped_slashes` option to the Ambassador module.

This is automated bump triggered from the source repo containing the updated Chart/Addon.

[d2iq-mergebot]

This repo has @mesosphere-mergebot integration. You can perform the following commands by submitting a comment. Submit a comment with content "@mesosphere-mergebot help" to view more detailed help text and examples. Be sure the have a look at the mergebot documentation, too.

@mesosphere-mergebot backport