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>

API Server/Dockerfile

@@ -28,13 +28,23 @@ RUN apk add --no-cache ca-certificates tzdata
 # Run as an unprivileged user.
 RUN addgroup -S app && adduser -S -G app app
 
-WORKDIR /app
-COPY --from=build /out/api-server /app/api-server
+COPY --from=build /out/api-server /usr/local/bin/api-server
+
+# The server writes two files relative to its working directory: plugins.json
+# (plugin enable-state + config) and .env, which the panel rewrites when a
+# superadmin retargets the PocketBase connection. Both must therefore live on a
+# writable, persistent path — hence /data, owned by the unprivileged user and
+# declared as a volume. A named volume mounted here inherits this ownership.
+RUN mkdir -p /data && chown app:app /data
+WORKDIR /data
+VOLUME /data
 
 # Config comes entirely from environment variables (see .env.example).
-# PB_ADMIN_EMAIL and PB_ADMIN_PASSWORD are required at startup.
-ENV PORT=8080
+# POCKETBASE_ADMIN_EMAIL / _PASSWORD are optional at startup: without them the
+# server still runs and a superadmin can configure the connection from the panel.
+ENV API_ADDR=:8080 \
+    PLUGINS_FILE=/data/plugins.json
 EXPOSE 8080
 
 USER app
-ENTRYPOINT ["/app/api-server"]
+ENTRYPOINT ["/usr/local/bin/api-server"]