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>

src/routes/api/servers/[name]/+server.ts

@@ -0,0 +1,15 @@
+import { json } from '@sveltejs/kit';
+import { destroyServer } from '$lib/server/fleet/create.js';
+
+export async function DELETE({ params }: { params: { name: string } }) {
+    const name = params.name;
+    if (!name) {
+        return json({ ok: false, error: 'server name required', kind: 'bad-request' }, { status: 400 });
+    }
+    const result = await destroyServer(name);
+    if (!result.ok) {
+        const status = result.kind === 'not-found' ? 404 : 500;
+        return json({ ok: false, error: result.message, kind: result.kind, warnings: result.warnings }, { status });
+    }
+    return json({ ok: true, warnings: result.warnings });
+}