Require Gitea login to write GPX data; IPv6-capable bind

Upload/delete/move/create-folder now require logging in via Gitea
OAuth2 (only MAPTOOL_ALLOWED_GITEA_USER is granted write access);
reading stays public. Deploy secrets (session secret, OAuth2 client
credentials, allowed user) are written to .env from Gitea Actions
repo secrets on every deploy instead of living on the server by hand.

Also switch the container's bind address to "[::]" (dual-stack) so
the app is reachable over IPv6, not just IPv4.

config/puma.rb

@@ -1,8 +1,9 @@
 # 127.0.0.1 by default: local-only, not exposed on the network (see
-# docs/architecture.adoc). The Docker deployment overrides this to 0.0.0.0
-# via BIND_HOST — inside a container, binding to loopback only would make
-# the app unreachable through the published port; Docker's own port
-# publishing is the network boundary there instead.
+# docs/architecture.adoc). The Docker deployment overrides this via
+# BIND_HOST (to "[::]", dual-stack IPv4+IPv6 — see docker-compose.yaml) —
+# inside a container, binding to loopback only would make the app
+# unreachable through the published port; Docker's own port publishing is
+# the network boundary there instead.
 bind "tcp://#{ENV.fetch('BIND_HOST', '127.0.0.1')}:#{ENV.fetch('PORT', 4567)}"
 
 environment ENV.fetch("RACK_ENV", "development")