♻️(helm) separate PostHog ingress

Based on feedback from @rouja, I've updated the Helm configuration for PostHog
to use separate ingress resources for each service. Although the documentation
suggests sharing the same ingress, the services have different externalName
values, which conflicts with the use of a vhost in the ingress annotations.
This change ensures proper service redirection by aligning each service with
its own ingress.

src/helm/env.d/dev/values.meet.yaml.gotmpl

@@ -102,3 +102,6 @@ posthog:
   ingress:
     enabled: false
 
+  ingressAssets:
+    enabled: false
+

src/helm/env.d/production/values.meet.yaml.gotmpl

@@ -138,3 +138,11 @@ posthog:
       kubernetes.io/ingress.class: nginx
       nginx.ingress.kubernetes.io/upstream-vhost: eu.i.posthog.com
       nginx.ingress.kubernetes.io/backend-protocol: https
+
+  ingressAssets:
+    enabled: true
+    host: product.visio.numerique.gouv.fr
+    annotations:
+      kubernetes.io/ingress.class: nginx
+      nginx.ingress.kubernetes.io/upstream-vhost: eu-assets.i.posthog.com
+      nginx.ingress.kubernetes.io/backend-protocol: https

src/helm/env.d/staging/values.meet.yaml.gotmpl

@@ -148,3 +148,11 @@ posthog:
       kubernetes.io/ingress.class: nginx
       nginx.ingress.kubernetes.io/upstream-vhost: eu.i.posthog.com
       nginx.ingress.kubernetes.io/backend-protocol: https
+
+  ingressAssets:
+    enabled: true
+    host: product.visio-staging.beta.numerique.gouv.fr
+    annotations:
+      kubernetes.io/ingress.class: nginx
+      nginx.ingress.kubernetes.io/upstream-vhost: eu-assets.i.posthog.com
+      nginx.ingress.kubernetes.io/backend-protocol: https