Phase 5: add connectivity service manifests — wireguard-ext, openvpn-client, tor

Each manifest declares container requirements (host network, NET_ADMIN) for
connectivity_manager.py to use when launching exit tunnel containers.

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

services/wireguard-ext/manifest.json

@@ -0,0 +1,22 @@
+{
+  "id": "wireguard-ext",
+  "name": "WireGuard External Exit",
+  "description": "Connect PIC as a WireGuard client to an external VPN server. Selected peers exit through this tunnel.",
+  "version": "1.0.0",
+  "author": "roof",
+  "image": "git.pic.ngo/roof/svc-wireguard-ext:latest",
+  "container_name": "cell-wg-ext",
+  "network_mode": "host",
+  "cap_add": ["NET_ADMIN"],
+  "sysctls": ["net.ipv4.ip_forward=1"],
+  "volumes": [
+    { "name": "wg-ext-config", "mount": "/etc/wireguard" }
+  ],
+  "env": [],
+  "caddy_route": null,
+  "iptables_rules": [],
+  "config_schema": [
+    { "key": "conf_text", "type": "textarea", "label": "WireGuard config (.conf)", "required": true }
+  ],
+  "requires_host_network": true
+}