fix: vscode.extensions.all API doesn't include any disabled extensions

VS Code's `extensions.all` API only gets enabled extensions and doesn't include disabled ones, which could prevent language configs being found. To fix, we completely remove getting the extensions from the vscode API, and instead get the extensions directly from the directories.

- Added the ability to get the built-in and user extensions directly from the directory on non-WSL systems (eg. Windows), but using the same way it gets extensions on WSL using the extension data path keys and `readExtensionsFromDirectory` method.

- Removed `vscode.extensions.all` API call from `findAllLanguageConfigFilePaths` method.

Author: yCodeTech

src/configuration.ts

@@ -306,9 +306,16 @@ export class Configuration {
 			extensions.push(...windowsBuiltInExtensions, ...windowsUserExtensions);
 		}
 
+		const userExtensionsPath = this.extensionData.get("userExtensionsPath");
+		const builtInExtensionsPath = this.extensionData.get("builtInExtensionsPath");
+
+		// Read the paths and create arrays of the extensions.
+		const userExtensions = this.readExtensionsFromDirectory(userExtensionsPath);
+		const builtInExtensions = this.readExtensionsFromDirectory(builtInExtensionsPath);
+
 		// Add all installed extensions (including built-in ones) into the extensions array.
 		// If running WSL, these will be the WSL-installed extensions.
-		extensions.push(...vscode.extensions.all);
+		extensions.push(...builtInExtensions, ...userExtensions);
 
 		// Loop through all installed extensions, including built-in extensions
 		for (let extension of extensions) {