🔧(livekit) use server instance deployed on a VM

Deploying LiveKit on Kubernetes is quite challenging when using a private cloud provider.
@rouja faced some issues while configuring the exposed port necessary for the
STUN and TURN servers to work when the user is connected to a network behind a firewall.

@rouja deployed quickly a temporary LiveKit instance on a VM with its own STUN and
TURN servers to avoid using the Google infrastructure.

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

@@ -92,7 +92,7 @@ backend:
       secretKeyRef:
         name: backend
         key: LIVEKIT_API_KEY
-    LIVEKIT_API_URL: https://livekit.beta.numerique.gouv.fr
+    LIVEKIT_API_URL: https://livekit-docker-1.beta.numerique.gouv.fr
 
   createsuperuser:
     command:

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

@@ -92,7 +92,7 @@ backend:
       secretKeyRef:
         name: backend
         key: LIVEKIT_API_KEY
-    LIVEKIT_API_URL: https://livekit.beta.numerique.gouv.fr
+    LIVEKIT_API_URL: https://livekit-docker-1.beta.numerique.gouv.fr
 
   createsuperuser:
     command:

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

@@ -92,7 +92,7 @@ backend:
       secretKeyRef:
         name: backend
         key: LIVEKIT_API_KEY
-    LIVEKIT_API_URL: https://livekit.beta.numerique.gouv.fr
+    LIVEKIT_API_URL: https://livekit-docker-1.beta.numerique.gouv.fr
 
   createsuperuser:
     command: