Add deploy + destroy server flow; migrate to t5_<mode>_<slug>_<n> naming

Full server lifecycle management from Electric Cherry: pick game/mode/map/pluto
key in the Fleet page, EC provisions the deployment via Komodo, allocates a
port in 28960-28980, creates the 0o777 host dir, and starts the container.
Destroy button tears everything down (Komodo Destroy+Delete, rm -rf host dir,
transactional DB cleanup) and surfaces any partial-failure warnings inline.

Same phase cuts over to the new naming scheme (t5_zombie_cosmodrome_1 etc.).
Komodo entity names now match EC server names 1:1 (no more _/- transform), and
the map catalog carries friendly/slug/canonical for each of the 11 t5 zombie
maps. Server rows gain game_mode, map_slug, host_dir, config_file, game_id,
image, created_by, and destroyed_at columns for provisioning + audit.

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

.env.example

@@ -14,6 +14,19 @@ DEPLOY_KEEP_DAYS=7
 KOMODO_ADDRESS=https://komodo.example.internal
 KOMODO_API_KEY=
 KOMODO_API_SECRET=
+# Komodo server (host) that new deployments land on. Must match the exact
+# name shown on the Servers page in the Komodo UI. Required to deploy new
+# servers from the Fleet page.
+KOMODO_TARGET_SERVER=
+# Optional overrides for the plutainer defaults used when EC creates a new
+# server. Change these if you fork the image or use a different docker network.
+# PLUTAINER_IMAGE=ghcr.io/ayymoss/plutainer:latest
+# PLUTAINER_NETWORK=komodo_default
+# PLUTAINER_GAMEFILES_VOLUME=t5_game_files
+# Port range EC picks from when auto-assigning a game_port to a new server.
+# Must correspond to what's actually forwarded on the Komodo host firewall.
+# SERVER_PORT_MIN=28960
+# SERVER_PORT_MAX=28980
 
 # RCON — shared across the fleet (every server uses the same rcon_password).
 # Host defaults to host.docker.internal so the container can reach game