feat: NPM remote mode for cross-machine deployments

- Add npm_remote setting: when enabled, proxy forwards to server_ip with
  published host ports instead of Docker container names
- Deployer looks up assigned host port via InspectContainerPort in remote mode
- Auto-remove stale containers with same name before creating new ones
- Add Remote NPM toggle with warning on NPM settings page
- DB migration + schema for npm_remote column

web/src/lib/i18n/en.json

@@ -373,7 +373,10 @@
     "testing": "Testing...",
     "testSuccess": "NPM connection successful",
     "testFailed": "NPM connection failed",
-    "saveFailedConnection": "Cannot save \u2014 connection test failed"
+    "saveFailedConnection": "Cannot save \u2014 connection test failed",
+    "remoteMode": "Remote NPM",
+    "remoteModeHelp": "Enable when NPM runs on a different machine than Docker. Forwards to Server IP with published host ports.",
+    "remoteModeWarning": "Requires Server IP in General settings. Ports are auto-mapped to random host ports."
   },
   "settingsCredentials": {
     "title": "Credentials",