Bring the Docker setup in line with DriverVault's

The combined stack now includes PocketBase as a first-class service instead
of assuming an external one: a Docker/pocketbase image built from the release
binary that bundles the pb_migrations and upserts the superuser on boot, so a
fresh stack checks/creates its collections and super-admin the same way
DriverVault does. Add production compose variants (registry images) and
.env(.prod).example files for both Docker/ and Docker AIO/, a top-level compose
name, a PocketBase healthcheck with a service_healthy dependency, and
env-driven ports. Move the containerized PocketBase to :8070 (the live remote
PB stays 10.2.1.10:8026). Add a root .dockerignore to trim the repo-root build
context used by the pocketbase and AIO images.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Docker AIO/.env.example

@@ -0,0 +1,21 @@
+# Copy to .env and fill in. Used by the Docker AIO docker-compose.yml.
+
+# --- PocketBase superuser (also used by the API Server to authenticate) ------
+POCKETBASE_ADMIN_EMAIL=admin@dji.local
+POCKETBASE_ADMIN_PASSWORD=djiadmin2026!
+
+# The app super-admin login (superadmin@pilotvault.local) is created by the
+# bundled PocketBase migrations on first boot.
+
+# Allowed CORS origin(s) — "*" is convenient for a local demo.
+CORS_ALLOW_ORIGINS=*
+
+# --- Host port mappings (optional; defaults shown) --------------------------
+WEB_PORT=8090
+API_PORT=8080
+PB_PORT=8070
+
+# --- Storage ----------------------------------------------------------------
+# Docker-managed named volume by default; set PB_DATA to an absolute host path
+# for a bind mount, e.g. PB_DATA=/srv/pilotvault/pb_data
+PB_DATA=pb_data