fix(vscode): bundle dependencies with esbuild to fix extension activation

[chupe]

Problem

The VS Code extension fails to activate with error:

Cannot find module 'vscode-languageclient/node'

The --no-dependencies flag in vsce package assumes dependencies are bundled into the output JS, but the build uses plain tsc which only transpiles without bundling.

Solution

• Replace tsc with esbuild for bundling all dependencies into a single minified file
• Add typecheck script to retain TypeScript type checking
• Move @types/* packages to devDependencies where they belong
• Add node_modules/ and **/*.map to .vscodeignore to keep package small

Result

• Extension now activates correctly
• Package size: 129 KB (vs 1.15 MB if bundling node_modules directly without esbuild)

Testing

1. Built and packaged extension with bun run package
2. Installed .vsix in VS Code
3. Verified extension activates and "Codebook" appears in Output panel
4. Confirmed spell checking works on supported file types

[chupe]

Hey folks, hope you don't mind the PR.

Thank you for your work, I really appreciate the convenience of using codebook across my editors.
I was having some issue trying to get it to work in VSCode. After root-causing it to a missing dependency after the build is completed I created the PR using Opencode/Claude.

Look forward to your feedback!

[blopker]

Very cool! I haven't used VSCode in a bit now, so progress on this has been slow. Thank you for checking it out. PR looks good. Please let me know if you run into any further issues!