feat: support publishing a container's port to host loopback

Some installations need to stay reachable by a native process on the
same host outside the manager's own proxy — e.g. a legacy nginx
location serving media/signed URLs for an app that also happens to be
an MCP server. Previously this required manually recreating the
container outside the manager's lifecycle (lost on the next
build/redeploy). publishHostPort makes it a real, persisted setting.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

apps/server/src/service/orchestrator.ts

@@ -56,6 +56,7 @@ export function configureInstallation(
     basicAuthUsername?: string | null;
     basicAuthPassword?: string | null;
     startCommand?: string | null;
+    publishHostPort?: number | null;
   },
 ): Installation {
   return updateInstallation(id, patch);