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>

tests/helpers/fixture.ts

@@ -15,7 +15,7 @@ export interface Fixture {
  * under test is imported. There's no shared/scripts directory anymore — the
  * upload-only model puts script content in the DB.
  */
-export async function newFixture(servers: string[] = ['t5_kino_1']): Promise<Fixture> {
+export async function newFixture(servers: string[] = ['t5_zombie_theater_1']): Promise<Fixture> {
     const root = await mkdtemp(join(tmpdir(), 'cherry-'));
     const t5 = join(root, 't5');
     const betaArchive = join(root, 'beta-archive');