feat: live updates move every server onto a new build without a restart

With new binaries in place, master moves everything onto them while the
server keeps running (the dashboard's Live update, /liveupdate or SIGUSR2 to
master):

- database migrations of the new build first; a failure stops there
- UGC finishes the jobs it is running (queued rows stay pending), auth
  restarts, chat hands its teams to master for the next chat server; master
  starts the new processes and retries ones that don't come back
- once the new chat server is up (CHAT_SERVER_READY) every world connects at
  once and sends its players again (LoginSessionNotify resync, no login logged)
- every world instance is replaced with an instance migration: public worlds
  and private ones (same password) at once, properties after the old instance
  saved and froze the property (MIGRATE_PREPARE: no building, claiming or
  saving there any more), activity zones and character select once their
  players left or after a wait; empty instances just stop, zones in
  prestart_worlds get a new one first
- the dashboard restarts last and picks the status up again

Players land where they stood (position carried in CarriedPlayerState, also on
properties and Moon Base). Draining instances get no new players
(InstanceMigration::AcceptsNewPlayers) and show as "Moving players" in the
world list. The order lives in LiveUpdateMachine.h without master state and is
unit tested; master's glue is LiveUpdateCoordinator. Master itself is not
replaced. Message IDs are appended only.

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

dUgcServer/UgcProcessor.h

@@ -61,6 +61,15 @@ public:
 	// Waits for the jobs that are running; queued ones are dropped (they stay pending in the database)
 	void Stop();
 
+	/**
+	 * Main thread, live updates: take no new work. Queued jobs are dropped (they stay pending in the database, so the
+	 * next UGC server makes them); the running ones finish and their outcome is recorded by Update as usual.
+	 */
+	void Drain();
+	// Main thread: draining and nothing running or waiting to be recorded any more
+	bool Drained() const;
+	bool IsDraining() const { return m_Draining; }
+
 	// Main thread: poll, dispatch, record results, keep the storage under its cap
 	void Update();
 
@@ -219,6 +228,7 @@ private:
 	double m_CpuSeconds{};
 	double m_CpuPercent{};
 	bool m_Stopping{};
+	bool m_Draining{};         // main thread: live update, no new work (Drain)
 	std::vector<std::thread> m_Threads;
 
 	// Main thread only