fix: use named volumes for indexer and processor databases

Both compose stacks declared their database data on anonymous volumes
(cockroach `- /cockroach/cockroach-data`, postgres `- /var/lib/postgresql/data`).
Anonymous volumes are bound to a specific container, so a service rename or
recreate (e.g. the recent db -> cockroachdb rename) orphans the old volume and
starts with empty data — forcing a full re-ingest/resync.

Switch both to named volumes (cockroach-data, postgres-data) so database data
survives renames and recreations.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: sameh-farouk

docker-compose.yml

@@ -10,7 +10,7 @@ services:
     ports:
       - "127.0.0.1:${DB_PORT}:5432"
     volumes:
-      - /var/lib/postgresql/data
+      - postgres-data:/var/lib/postgresql/data
     environment:
       POSTGRES_USER: ${DB_USER}
       POSTGRES_PASSWORD: ${DB_PASS}
@@ -48,3 +48,6 @@ services:
       - 4000:4000
     depends_on:
       - db
+
+volumes:
+  postgres-data:

indexer/docker-compose.yml

@@ -12,7 +12,7 @@ services:
       - "127.0.0.1:8080:8080"
     command: start-single-node --insecure
     volumes:
-      - /cockroach/cockroach-data
+      - cockroach-data:/cockroach/cockroach-data
 
   cockroachdb-init:
     depends_on:
@@ -75,3 +75,6 @@ services:
       DB_USER: "root"
     ports:
       - "4444:3000"
+
+volumes:
+  cockroach-data: