[installer] Run the toxic-config component as a sidecar in the Toxiproxy pod

[andrew-farries]

Description

As part of #9198 we will run a Toxiproxy instance in the application cluster to allow us to simulate a high-latency connection to the Gitpod database.

#14473 added a new component, toxic-config, intended to run as a sidecar container in a Kubernetes pod alongside Toxiproxy, that configures a given proxy with a latency toxic.

This PR makes that new component run as a sidecar in the Toxiproxy component to ensure that the mysql component is configured with latency.

Related Issue(s)

Part of #9198

How to test

1. Port forward to Toxiproxy:

kubectl port-forward svc/toxiproxy 8474:8474

2. Verify that the sidecar container successfully configured the mysql proxy:

kubcectl logs deploy/toxiproxy -c toxic-config

3. Verify that the mysql proxy has been configured with a latency toxic:

docker run --rm --net=host --entrypoint="/toxiproxy-cli" -it ghcr.io/shopify/toxiproxy inspect mysql

Release Notes

NONE

Documentation

Werft options:

• /werft with-local-preview
  If enabled this will build install/preview
• /werft with-preview
• /werft with-slow-database
• /werft with-large-vm
• /werft with-integration-tests=all
  Valid options are all, workspace, webapp, ide

[werft-gitpod-dev-com]

started the job as gitpod-build-af-run-toxic-config-sidecar.17 because the annotations in the pull request description changed
(with .werft/ from main)