refactor: istio-sidecar injection into supabase pods

[CollectiveUnicorn]

Describe what should be investigated or refactored

Remove sidecar.istio.io/inject: "false" from the Supabase bitnami-values.yaml and resolve any issues with the pods starting up with the istio sidecar.

Additional context

At present, the istio sidecar is suppressed from being injected into the Supabase pods due a conflict with the Supabase wait-for-db init container. The issue prevents pods from starting up when istio-injection is enabled. Enabling injection will cause the pods to wait for a connection to the db that cannot be made due to postgres starting up with the istio sidecar before the pods have their sidecar's injected. This causes all the pods to hang indefinitely.

[CollectiveUnicorn]

Blocked by #380

[YrrepNoj]

Related to #473

[CollectiveUnicorn]

Some possible solutions:

• Running istio in ambient mode: https://istio.io/latest/docs/ops/ambient/getting-started/
• Modify or remove wait-for-db
• Manually inject the istio sidecar via the istioctl tool
• Wait to do the istio sidecar injection until wait-for-db finishes
• Permissive mode on startup so that the wait-for-db postgres connection is successful even after the sidecar is injected

[justinthelaw]

Blocked by #968