feat: Audit ingress to a different webserver

[sunib]

Reworking a lot stuff:

• Improving my own understanding of docker-in-docker and docker-out-docker
• Have a seperate HTTP(S) endpoint where kubernetes-api can stream audit events (allows to have different TLS configuration when needed).
• Allow audit event ingress from more than 1 kubernetes-api clusters
• Remove all half-baked HA support (we will re-introduce that properly when the time comes)
• Run the install for both the single-yaml and helm chart in the pipeline (smoke test).
• Dropping the need for network=host
• Better support for caching of golang mod
• Somehow managed to still push secrets into git: that's now really prevented (also with an e2e test). Also added the plan to add sops into the mix.

[gitguardian]

️✅ There are no secrets present in this pull request anymore.

If these secrets were true positive and are still valid, we highly recommend you to revoke them.
While these secrets were previously flagged, we no longer have a reference to the
specific commits where they were detected. Once a secret has been leaked into a git
repository, you should consider it compromised, even if it was deleted immediately.
Find here more information about risks.

---

^{_{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}}