Configure TypeScript language server and development environment

# TypeScript Support

## Current Status
- [x] Codelens (current keymaps: `cL` refresh, `cr` run action)
- [x] Go to definition (current keymap: `gD` go to source definition)

## LSP Configuration Issue

**Problem**: LazyVim TypeScript extra conflicts with custom vtsls configuration
- LazyVim extra (`lazyvim.plugins.extras.lang.typescript`) tries to use `typescript-language-server`
- Custom LSP config uses `vtsls` and disables `tsserver`/`ts_ls`
- Results in EACCES permission error: `typescript-language-server` not found

**Current Setup**:
- `vtsls` installed via Mason
- Custom LSP configuration in `lua/plugins/lsp.lua`
- LazyVim TypeScript extra imported in `lazy.lua:20`

**Options**:
1. **Install both**: Keep LazyVim extra + install `typescript-language-server` alongside `vtsls`
2. **Override LazyVim**: Modify extra to use `vtsls` instead
3. **Document differences**: Research which LSP provides which specific functionality

**Need to determine**:
- Which features come from LazyVim TypeScript extra vs custom vtsls config
- What functionality would be lost by removing the LazyVim extra
- Performance impact of running multiple TypeScript LSPs

**Files involved**:
- `lua/config/lazy.lua` - LazyVim extra import
- `lua/plugins/lsp.lua` - Custom vtsls configuration
- Mason-installed tools: `vtsls` (working), `typescript-language-server` (missing)