Allow importModuleSpecifier: "relative" to be overridden for explicitly configured "paths" in a jsconfig/tsconfig

This is a follow-up issue of https://github.com/microsoft/TypeScript/issues/40139

As per the docs, once you've imported a variable somewhere, vscode knows where to find it (bypassing the issue above).

I want all my code to be imported with relative imports everywhere for consistency. so I set "javascript.preferences.importModuleSpecifier": "relative". However, I don't want relative paths to be used when importing from a module declared in tsconfig's paths, as I specifically put it there so it can be resolved as an absolute import for convenience.

Clearly these 2 settings are conflicting, but I wonder if the current compromise is the best one (i.e. settings.json wins over tsconfig)?

I would expect to be able to auto-import variables from my paths module absolutely, even though I want everything else to import relatively.

• VSCode Version: Insiders
• OS Version: macOS 10.15.6

Steps to Reproduce:

1. Clone this repo: https://github.com/Floriferous/paths-resolution
2. Go to branch absolute-import-paths
3. Notice test2.js imports someVar properly
4. Open test.js, try to auto-import someVar, notice intellisense only suggests a relative import

Does this issue occur when all extensions are disabled?: Yes

从复现路径解析开始，重点关注 test.js、test2.js 以及所引用的 jsconfig/tsconfig paths 配置；启用相对路径优先后，复现自动导入建议。跟踪对显式配置路径的自动导入处理。完成的标准是：基于 paths 的导入应以绝对路径形式被建议，而其他导入仍保持相对路径。