🔨(helm) update helm chart for custom background image

Add media_files_svc and ingress_media_files to helm chart
for serving medias related to the new files.

This setup is more straightforward than merging the
existing recording related media ones.

Also updated values to enable file upload by default in dev.

Mostly done by @lebaudantoine.

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

@@ -64,6 +64,7 @@ backend:
     AWS_S3_SECRET_ACCESS_KEY: password
     AWS_STORAGE_BUCKET_NAME: meet-media-storage
     AWS_S3_REGION_NAME: local
+    AWS_S3_SIGNATURE_VERSION: s3v4
     MEDIA_BASE_URL: https://meet.127.0.0.1.nip.io
     RECORDING_ENABLE: True
     RECORDING_STORAGE_EVENT_ENABLE: True
@@ -80,6 +81,8 @@ backend:
     APPLICATION_JWT_AUDIENCE: https://meet.127.0.0.1.nip.io/external-api/v1.0/
     APPLICATION_JWT_SECRET_KEY: devKeyApplication
     APPLICATION_BASE_URL: https://meet.127.0.0.1.nip.io
+    FILE_UPLOAD_ENABLED: True
+    AWS_S3_DOMAIN_REPLACE: https://minio.127.0.0.1.nip.io
 
 
   migrate:
@@ -311,3 +314,18 @@ ingressMedia:
 serviceMedia:
   host: minio.meet.svc.cluster.local
   port: 9000
+
+
+ingressMediaFiles:
+  enabled: true
+  host: meet.127.0.0.1.nip.io
+
+  annotations:
+    nginx.ingress.kubernetes.io/auth-url: https://meet.127.0.0.1.nip.io/api/v1.0/files/media-auth/
+    nginx.ingress.kubernetes.io/auth-response-headers: "Authorization, X-Amz-Date, X-Amz-Content-SHA256"
+    nginx.ingress.kubernetes.io/upstream-vhost: minio.meet.svc.cluster.local:9000
+    nginx.ingress.kubernetes.io/rewrite-target: /meet-media-storage/files/$1
+
+serviceMediaFiles:
+  host: minio.meet.svc.cluster.local
+  port: 9000