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/logs.py

@@ -31,7 +31,11 @@ async def get_logs(
         config = load_config(root)
         # A name may span kinds — the managed (systemd) one owns the journal.
         dep_kind = next(
-            ((k, s) for k, s in config.deployments_named(name) if getattr(s, "manage", None)),
+            (
+                (k, s)
+                for k, s in config.deployments_named(name)
+                if getattr(s, "manage", None)
+            ),
             None,
         )
         if dep_kind is None: