build(#19): flip kin-lsp path->registry dep (now published to kin registry)

kin-lsp 0.1.0 is published to the kin registry, so the committed manifest no
longer needs the ../kin-lsp path dep — a clean external/Linux clone resolves it
from the registry like every other kin-* crate. Local dev is unaffected: the
gitignored .cargo/config.toml [patch.kin] pins kin-lsp back to ../kin-lsp.
Closes the last clean-clone gap (#13).

Author: troyjr4103

Cargo.lock

@@ -135,7 +135,7 @@ kin-daemon = { path = "crates/kin-daemon" }
 kin-mcp = { path = "crates/kin-mcp" }
 kin-spine = { path = "crates/kin-spine" }
 kin-registry = { path = "crates/kin-registry" }
-kin-lsp = { path = "../kin-lsp" }
+kin-lsp = { version = "0.1.0", registry = "kin" }
 kin-pipelines = { path = "crates/kin-pipelines" }
 # Cross-platform base: NO "metal" here. `[workspace.dependencies]` entries cannot be
 # `[target.'cfg(...)']`-gated, so listing "metal" here forces the macOS-only kin-infer/metal