🐛(helm) bump the dev-backend chart to run silo

The dev-backend chart 0.0.10 started the media storage with a hardcoded
`minio server` shell command and pulled quay.io/minio/mc to create the
bucket. Since the switch to pgsty/silo, the first one failed with
"minio: command not found" and the second one with a 401 from quay.io, so
the feature deployments (ArgoCD) did not come up.

Chart 0.0.15 defaults to pgsty/silo and pgsty/mc, and starts the container
with `args` instead of a shell command, so the name of the executable no
longer matters.

documentation/examples/helm/minio.values.yaml

@@ -1,6 +1,8 @@
 minio:
   enabled: true
   image: pgsty/silo
+  mc:
+    image: pgsty/mc
   name: minio
   # serviceNameOverride: docs-minio
   ingress:

src/helm/env.d/dev/values.dev-backend.yaml.gotmpl

@@ -13,6 +13,8 @@ redis:
 minio:
   enabled: true
   image: pgsty/silo
+  mc:
+    image: pgsty/mc
   name: minio
   ingress:
     enabled: true

src/helm/env.d/feature/values.dev-backend.yaml.gotmpl

@@ -12,6 +12,8 @@ redis:
 minio:
   enabled: true
   image: pgsty/silo
+  mc:
+    image: pgsty/mc
   name: minio
   ingress:
     enabled: true

src/helm/helmfile.yaml.gotmpl

@@ -1,12 +1,12 @@
 environments:
   dev:
     values:
-      - version: 6.0.0-alpha.2
+      - version: 6.0.0
         # a Prometheus scraping the metrics of the backend and of yhub
         monitoring: true
   feature:
     values:
-      - version: 6.0.0-alpha.1
+      - version: 6.0.0
         feature: ci
         domain: example.com
         imageTag: demo
@@ -24,7 +24,7 @@ releases:
   - name: dev-backend
     namespace: {{ .Namespace }}
     chart: dev-backends/dev-backend
-    version: 0.0.10
+    version: 0.0.15
     values:
       - env.d/{{ .Environment.Name }}/values.dev-backend.yaml.gotmpl