BM-2026: switch redis to latest valkey (#1383)

Testing different cases, but the storage layout seems to be compatible
and non-breaking, so keeping the same volume to avoid issues when
upgrading during an in-progress proof, unless we notice this being
breaking for anyone.

Author: austinabell

.env.broker-template

@@ -3,7 +3,7 @@
 RUST_LOG=info
 
 REDIS_HOST=redis
-REDIS_IMG=redis:7.2.5-alpine3.19
+REDIS_IMG=valkey/valkey:9.0
 
 POSTGRES_HOST=postgres
 POSTGRES_IMG=postgres:16.3-bullseye

compose.yml

@@ -84,13 +84,13 @@ x-broker-common: &broker-common
 services:
   redis:
     hostname: ${REDIS_HOST:-redis}
-    image: ${REDIS_IMG:-redis:7.2.5-alpine3.19}
+    image: ${REDIS_IMG:-valkey/valkey:9.0}
     restart: always
     ports:
       - 6379:6379
     volumes:
       - redis-data:/data
-    command: redis-server --maxmemory-policy allkeys-lru --save 900 1 --appendonly yes
+    command: valkey-server --maxmemory-policy allkeys-lru --save 900 1 --appendonly yes
     healthcheck:
       test: ["CMD", "redis-cli", "ping"]
       interval: 5s