api+ui: kind-scoped save/delete endpoints and links

API: /config/{services,jobs,tools,static}/{name} now pin the twin they
target — _save_deployment/_delete_deployment take an explicit kind so a
patch to a 'backup' service can't bleed into a 'backup' job/tool. Add
/tools and /static endpoints; keep /deployments/{name} kind-agnostic.
New test_kind_twins proves per-kind save/delete isolation on disk.

UI: ConfigPanel and CreateDeploymentForm write to the kind-scoped
resource; GatewayPanel/NodeDetail/DeploymentsSection link via a shared
detailPath(name, kind) helper instead of the ambiguous /deployment/:name.

Includes incidental ruff-format reflow of untouched api files.

castle-api/src/castle_api/mesh.py

@@ -40,7 +40,9 @@ class MeshStateManager:
     def update_node(self, hostname: str, registry: NodeRegistry) -> None:
         """Add or update a remote node's registry."""
         self._nodes[hostname] = RemoteNode(registry=registry)
-        logger.info("Mesh: updated node %s (%d deployed)", hostname, len(registry.deployed))
+        logger.info(
+            "Mesh: updated node %s (%d deployed)", hostname, len(registry.deployed)
+        )
 
     def set_offline(self, hostname: str) -> None:
         """Mark a node as offline (LWT received)."""