chore(services): exclude nominatim and elasticsearch volumes from backups

Both contain deterministic indexes built from the OSM PBF that the
data-manager already downloads and hardlinks into infra/docker/data/.
The other heavy region-derived services (valhalla, motis, photon,
tileserver, overpass) all use bind-mounted infra/docker/data/<svc>/
without backup flags for the same reason — Nominatim and Pelias just
historically used named volumes.

Backups for these can hit ~100 GB each per snapshot for a Germany-
sized deployment, completely dominating snapshot size and prune cost
while saving only a 1–4h (Nominatim) or ~8h (ES/Pelias) rebuild on
disaster recovery — and during DR you'd typically want a fresh OSM
update anyway, which would invalidate the backed-up indexes.

The truly irreplaceable layers — postgis (auth/vault/audit), redis
(transit registry, app cache), traefik (ACME state) — keep
backup: true.

Author: Medformatik

services/elasticsearch/service.json

@@ -26,7 +26,7 @@
     }
   },
   "volumes": [
-    { "name": "openmapx-esdata", "mountAt": "/usr/share/elasticsearch/data", "backup": true }
+    { "name": "openmapx-esdata", "mountAt": "/usr/share/elasticsearch/data", "backup": false }
   ],
   "exposure": {
     "hostPorts": [{ "container": 9200, "host": 9200, "bindAddress": "127.0.0.1" }]

services/nominatim/service.json

@@ -48,9 +48,9 @@
     {
       "name": "openmapx-nominatim-data",
       "mountAt": "/var/lib/postgresql/16/main",
-      "backup": true
+      "backup": false
     },
-    { "name": "openmapx-nominatim-flatnode", "mountAt": "/nominatim/flatnode", "backup": true }
+    { "name": "openmapx-nominatim-flatnode", "mountAt": "/nominatim/flatnode", "backup": false }
   ],
   "exposure": {
     "hostPorts": [{ "container": 8080, "host": 8088, "bindAddress": "127.0.0.1" }]