Docker: persist API Server state, wire up OCPP, drop legacy env names

Audited every Dockerfile, compose file and .env.example against the code
they deploy. Four things had drifted:

Persistence. The API Server writes plugins.json and rewrites .env (the
panel's retarget-PocketBase flow) relative to its working directory,
which was a root-owned /app while the process runs as the app user - so
both writes failed, and no volume was declared to keep them anyway. The
binary moves to /usr/local/bin and the working directory becomes a /data
volume owned by app. The AIO image gets the same via directory=/data on
its supervisord program.

OCPP. Charger control was undeployable: OCPP_REQUIRE_TLS defaults to true
and appeared in no Docker file, so a charger dialling the plain-HTTP
/ocpp/{serial} was rejected with nothing explaining why. Both OCPP vars
are now threaded through the compose files and env examples, with the
reasoning (the per-charger control token rides in a Basic-auth header).

CORS. API Server/docker-compose.yml defaulted to localhost:5173, the Vite
dev port, where every other file uses 8090.

Env names. .env.example has called PB_URL/PB_ADMIN_*/PORT legacy for a
while, but the Docker layer still used them. Container-side names are now
POCKETBASE_*/API_ADDR; the .env keys operators set stay PB_ADMIN_* so
existing .env files keep working.

Left alone deliberately: alpine:latest stays unpinned (cannot verify
current tags or test the build from here), and the golang/node bases
already match go.mod and Vite 8's floor.

Validated as YAML only - there is no Docker CLI on this machine, so no
image was built and the /data ownership fix follows standard volume
semantics rather than an observed run.

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

Docker/.env.prod.example

@@ -32,6 +32,18 @@ PB_BOOTSTRAP=true
 CORS_ALLOW_ORIGINS=http://localhost:8090
 AUTH_USERS_COLLECTION=users
 
+# --- EV charging control (Anker Solix, OCPP) ---------------------------------
+# Only relevant when a charger is set to own/proxy control mode. The charger
+# dials in to /ocpp/{serial} on the API Server port, carrying its control token
+# in an OCPP Basic-auth header — which a plaintext ws:// would expose, so
+# non-TLS connections are rejected by default. Keep the default and terminate
+# TLS in a reverse proxy in front of this stack, setting OCPP_PUBLIC_URL to the
+# public wss:// base the charger should be pointed at (deriving it from request
+# headers is unreliable behind a proxy). Turning the check off is for trusted
+# networks only.
+OCPP_REQUIRE_TLS=true
+OCPP_PUBLIC_URL=
+
 # --- Ports -------------------------------------------------------------------
 # WEB_PORT is the public front door (bound on all interfaces).
 WEB_PORT=8090
@@ -43,7 +55,10 @@ API_PORT=8080
 API_BIND=127.0.0.1
 
 # --- Storage -----------------------------------------------------------------
-# Default is a Docker-managed named volume ("pb_data"). To store the database on
-# a host path instead, set PB_DATA to an absolute path, e.g.:
-#   PB_DATA=/srv/drivervault/pb_data
+# Defaults are Docker-managed named volumes. To store either on a host path
+# instead, set it to an absolute path, e.g. PB_DATA=/srv/drivervault/pb_data.
+# PB_DATA  — the PocketBase database and uploads.
+# API_DATA — the API Server's plugins.json and the .env the panel writes back
+#            when a superadmin retargets the PocketBase connection.
 PB_DATA=pb_data
+API_DATA=api_data