Remove allow_transport from network permissions (#55)

Author: danbarr

docs/toolhive/guides-cli/custom-permissions.mdx

@@ -50,8 +50,6 @@ Profiles include the following sections:
       period (e.g., `.github.com` allows any subdomain of `github.com`).
       Wildcards are not supported.
     - `allow_port`: List of allowed ports for outbound connections.
-    - `allow_transport`: List of allowed transport protocols (e.g., `tcp`,
-      `udp`).
 
 ## Default permissions in the ToolHive registry
 
@@ -129,7 +127,6 @@ For example:
   "network": {
     "outbound": {
       "insecure_allow_all": false,
-      "allow_transport": ["tcp", "udp"],
       "allow_host": ["localhost", ".google.com"],
       "allow_port": [80, 443]
     }
@@ -142,8 +139,8 @@ This profile:
 - Allows read-only access to `/example/path1` and `/example/path2`
 - Allows read and write access to `/example/path3` (note that the `write`
   setting also implies read access)
-- Allows outbound TCP or UDP connections to `localhost` and `google.com`
-  (including subdomains) on ports 80 and 443
+- Allows outbound connections to `localhost` and `google.com` (including
+  subdomains) on ports 80 and 443
 
 ## Apply a permission profile
 
@@ -312,7 +309,6 @@ Enterprise instance:
      "network": {
        "outbound": {
          "insecure_allow_all": false,
-         "allow_transport": ["tcp"],
          "allow_host": ["github.example.com"],
          "allow_port": [443]
        }