feat: add provisioning lifecycle actions

Rename Deployments to Provisioning with compatible redirects and APIs. Add durable Start, Restart, Stop, and Rebuild operations alongside Create and Destroy; rebuild wipes the instance and recreates it in the same slot and port.

Add lifecycle, migration, recovery, and Komodo command tests. Type checks and production build pass; the full suite retains a telemetry assertion failure reproduced on the unchanged branch.

Refs #39

docs/deployment-blueprints.md

@@ -1,6 +1,6 @@
 # Deployment blueprints
 
-The Deployments page is the starting point for reusable server collections. A
+The Provisioning page is the starting point for reusable server collections. A
 blueprint describes a whole lineup: for example, two Kino lobbies, one Moon lobby,
 and two Town lobbies. Counts are desired fleet totals: existing and queued
 servers count toward each target, and only missing servers are created.
@@ -23,7 +23,7 @@ It fills deficits without changing existing servers' files.
 
 ## Build and launch a collection
 
-1. Choose **Create blueprint** on Deployments and name the lineup.
+1. Choose **Create blueprint** on Provisioning and name the lineup.
 2. Add maps from Black Ops I or II and set the desired total lobbies for each.
 3. Choose **Save & preview** (or **Preview fleet changes** on a saved blueprint).
    Choose **Fill missing servers** or **Match blueprint exactly**, then review
@@ -113,7 +113,7 @@ operation links back to its collection.
 
 ## Create and review a launch
 
-1. Choose **Single server** on Deployments (or the deploy action on the fleet).
+1. Choose **Single server** on Provisioning (or the deploy action on the fleet).
 2. Choose the current promoted setup and select a game/map, or select a blueprint.
 3. Choose **Preview launch**. Review the image reference, configuration sources,
    managed files and versions, selected map, lobby, port, and prerequisite checks.