Fixes #35395

Adds a TS Server option (to be specified in .vscode/settings.json) called autoImportFileExcludePatterns. The format is identical to tsconfig.json exclude specs, except I plan to do the following normalization on the VS Code side before sending to TS Server:

• Relative paths will be resolved relative to the folder VS Code has opened.
• Paths starting with a * will be prefixed with /, e.g. "**/node_modules/aws-sdk" will become "/**/node_modules/aws-sdk"
• Non-rooted paths (e.g. "node_modules/aws-sdk") will be prefixed with /**/ to match any directory prefix.

It’s also worth noting how this setting affects ambient modules and module augmentations (autoImportFileExcludePatterns3.ts in the tests). While the input to this setting refers to files, I’ve chosen to limit the granularity at which we filter to be per-module, not per-export. That means if more than one file declares an ambient module "foo", you can’t exclude the exports declared in just one of those files. We end up calling getMergedSymbol on these modules before looking at their individual exports, so we see all the exports from many files lumped together. (Keep in mind this setting does not exclude anything from your program, so excluded files in this setting still contribute to overall program knowledge.) If you wanted that kind of granularity, we’d have to look at the declarations of each export and evaluate the regexes against those rather than just doing it at the file level. With the right memoization, that might be possible, but I’d prefer to wait and see if there’s demand for it. As it is, to exclude an ambient module, the exclude patterns have to match every file that declares it, and its exports are either all included or all excluded.