test: exclude TypeScriptSupport LSP extension from test windows

The TypeScriptSupport extension auto-starts a real vtsls language server and
registers global providers (hover/QuickView, linting/CodeInspection, hints,
jump-to-def) for js/jsx/ts/tsx. In the test runner this polluted pre-existing
integration tests that assume nothing else is registered for those languages:

- QuickView: a removed JS hover provider still returned a popover (ours).
- ESLint: jsx files gained an active inspector, so inspection-disabled was false.
- PreferencesManager: real server spawn + doc-sync churn timed the spec out.

Strip it in test windows, matching the existing convention for the heavyweight
Git extension (excluded for the same reason in ExtensionLoader).

Author: abose

src/utils/ExtensionLoader.js

@@ -166,10 +166,16 @@ define(function (require, exports, module) {
         // we dont load the heavy weight git extension by default for tests as huge number
         // of tests written before git integration and too hard to fix those failing tests for now.
         // we will just have new tests from git specific workflows.
-        const index = DefaultExtensionsList.indexOf("Git");
-        if(index !== -1) {
-            DefaultExtensionsList.splice(index, 1);
-        }
+        // TypeScriptSupport is excluded for the same reason: it spawns a real vtsls language
+        // server and registers global providers (hover/QuickView, linting/CodeInspection,
+        // hints, jump-to-def) for js/jsx/ts/tsx, which breaks pre-existing integration tests
+        // (e.g. QuickView, ESLint) that assume nothing else is registered for those languages.
+        ["Git", "TypeScriptSupport"].forEach(function (extName) {
+            const index = DefaultExtensionsList.indexOf(extName);
+            if(index !== -1) {
+                DefaultExtensionsList.splice(index, 1);
+            }
+        });
     }
 
     const customExtensionLoadPaths = {};