[Chore] Use named network option for kathmandunet

Problem: Octez v14.0 supports kathmandunet as a named network,
but in our definitions we still use a network config.

Solution: update the node Formula and package definition to use
the named option for the kathmandu network.

Formula/tezos-node-kathmandunet.rb

@@ -26,14 +26,14 @@ def install
           "$node" config init \
                   --data-dir "$DATA_DIR" \
                   --rpc-addr "$NODE_RPC_ADDR" \
-                  --network=https://teztnets.xyz/kathmandunet \
+                  --network=kathmandunet \
                   "$@"
       else
           echo "Updating the node configuration..."
           "$node" config update \
                   --data-dir "$DATA_DIR" \
                   --rpc-addr "$NODE_RPC_ADDR" \
-                  --network=https://teztnets.xyz/kathmandunet \
+                  --network=kathmandunet \
                   "$@"
       fi
 
@@ -82,6 +82,6 @@ def plist
   end
   def post_install
     mkdir_p "#{var}/lib/tezos/node-kathmandunet"
-    system "tezos-node", "config", "init", "--data-dir" "#{var}/lib/tezos/node-kathmandunet", "--network", "https://teztnets.xyz/kathmandunet"
+    system "tezos-node", "config", "init", "--data-dir" "#{var}/lib/tezos/node-kathmandunet", "--network", "kathmandunet"
   end
 end

docker/package/packages.py

@@ -19,7 +19,7 @@
     "mainnet": "mainnet",
     "jakartanet": "jakartanet",
     "ghostnet": "ghostnet",
-    "kathmandunet": "https://teztnets.xyz/kathmandunet",
+    "kathmandunet": "kathmandunet",
 }
 networks_protos = {
     "mainnet": ["013-PtJakart"],