vscode-api-tests: use explicit "types" instead of "typeRoots"
Switches tsconfig from typeRoots-only (which only auto-includes @types/* found at the literal path ./node_modules/@types) to an explicit "types" list. Explicit types resolve via Node module resolution, so they keep working regardless of whether npm hoists @types/node to the workspace root or keeps it extension-local.
Refs microsoft/vscode-engineering#2912 — the recurring TS2591 "Cannot find name 'process'" failure on the build agent after #319389 changed the lockfile is consistent with @types/node being hoisted to a path the typeRoots-only config can't see. Matches the pattern already used by extensions/github, extensions/copilot, etc.
For #271167
This makes it so our built-in extensions can mostly be built using `tsc` on the command line. Previously the extensions were picking up a lot of typing info from the root `node_modules` that meant they weren't truly independent
**Bug**
Most VSCode extensions currently specify `"exclude"` in their `tsconfig.json` but not `"include"`. This may result in extra files being included in each project
**Fix**
Add `"include": ["src/**/*"]` to all extension tsconfig files
* Remove unneeded d.ts files from extensions
Moves most extensions to use the lib files for the standard library that typescript provides.
* Remove a few more node.d.ts references
Bryan ChenandGitHub
Matt Bierner
Johannes Rieken
Matt Bierner
Erich Gamma