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

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ --> <!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ --> <!-- Please search existing issues to avoid creating duplicates. --> <!-- Also please test using the latest insiders build to make sure your issue has not already been fixed: https://code.visualstudio.com/insiders/ --> 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. <!-- Use Help > Report Issue to prefill these. --> - 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 3. Open `test.js`, try to auto-import `someVar`, notice intellisense only suggests a relative import <!-- Launch with `code --disable-extensions` to check. --> Does this issue occur when all extensions are disabled?: Yes