feat(deploy): instances keep their dictionaries current, weekly, by themselves

EDRDG's licence asks of a server showing its dictionaries that it update
them at least monthly. The instance now does it alone: a `dictionaries`
service in compose, built from the curator (halkyon_learn_curator/
Dockerfile, its own unprivileged user 10001, 1 GB at most), runs `curate
update --every 7`, downloading EDRDG's files of the day once its files are
a week old and replacing them in a volume the server mounts read-only.
The curator never enters the server's image or process (decided
2026-10-09: a container of its own, weekly). The server rereads the
folder daily at 04:07 (DictionaryReloadFutureCall), loading what changed,
and loads now run one at a time. redeploy.sh builds both images.

An operator who'd rather supply the files removes the service and mounts
deploy/dictionaries/ into the server, as compose.yaml says.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MMm7usAo6q9ZZRoPkWjoxi
Signed-off-by: Tizian 「ティツィアーン」 <raisondetredev@pm.me>

deploy/redeploy.sh

@@ -58,7 +58,7 @@ main() {
   trap 'git reset -q --hard "$deployed"; echo "The checkout is back at $deployed." >&2' EXIT
   cd deploy
   # Build while the running server keeps serving; then dump, migrate, switch.
-  docker compose build -q server
+  docker compose build -q server dictionaries
   dump
   # Migrations as a run of their own, before the switch: Serverpod's maintenance role
   # applies them and exits with 0 only if that worked. Each migration is one