Support Native Kubernetes sidecars in our Chart

### Body

The 1.28 version of K8S introduce "naative sidecars" https://kubernetes.io/blog/2023/08/25/native-sidecar-containers/ which - with implementation of [KEP-753](https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/753-sidecar-containers/README.md) finally solve the long standing problem of sidecar lifetime management, where exiting the main container would not stop the POD where sidecar container is still running. We could likely also use some more features of sidecars.

Implementing some of our sidecars (for example kerberos, but also other sidecars that we currently use) would sovle the problems of side-car containers not being killed when main container shuts down, allowing to have better self-maintained k8s deployment.

It would be great to review our helm chart and apply the new sidecar pattern (for k8s >= 1.28).

### Committer

- [X] I acknowledge that I am a maintainer/committer of the Apache Airflow project.

Start by reviewing the project’s Helm chart and the Kubernetes 1.28 native sidecar documentation and KEP-753, then identify how current sidecars such as Kerberos are defined. Done means applicable sidecars use the native pattern for Kubernetes 1.28 and newer, with their lifecycle managed when the main container exits.

Written by the indexing model from the issue text.