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>

.dockerignore

@@ -0,0 +1,27 @@
+# Root build-context ignore. The pocketbase and Docker AIO images build with the
+# repo root as their context (they COPY from "API Server/" and "Web App/"), so
+# keep the context lean: only those two trees plus Docker/pocketbase are needed.
+
+# Sibling apps unrelated to the server images.
+Adobe Plugin/
+Design/
+Fly App/
+Phone App/
+
+# Frontend deps + generated bundles — rebuilt inside the images.
+**/node_modules/
+**/dist/
+
+# Secrets & local build artifacts — never send to the build context.
+**/.env
+plugins.json
+*.exe
+*.exe~
+*.log
+
+# VCS / editor / tooling noise.
+.git/
+.gitignore
+.claude/
+.vscode/
+.idea/