Bundle dingo-lsp with vscode extension

[ncsurfus]

Currently, users must manually download and provide the LSP path when using the vscode extension (as shown below). By bundling the extension, or providing a mechanism to automatically download it, the barrier to entry can be decreased which may help improve adoption.

{
  "dingo.lsp.path": "/full/path/to/dingo-lsp"
}

[dingo-reviewer]

@ncsurfus You're right that the current setup is friction-heavy. Right now lspClient.ts just shells out to whatever dingo.lsp.path resolves to (defaulting to dingo-lsp on $PATH), and if it's missing you get a generic "binary not found" error with a link to the install docs.

There are two realistic approaches here:

• Bundled binaries — ship platform-specific dingo-lsp binaries inside the .vsix (like rust-analyzer does). Bigger package, but zero setup.
• Auto-download on activation — detect missing binary, fetch the right one from GitHub releases, and cache it in the extension's globalStoragePath. Smaller package, but needs release infrastructure.

The auto-download route is probably the better first step since we already have the error-handling path in editors/vscode/src/lspClient.ts (lines 150-159) that detects the missing binary — that's a natural place to hook in a download prompt instead of just showing an error.

Would you be interested in contributing this? The extension TypeScript is straightforward and it'd be a solid first contribution.