Remove optionalDependencies from API npm package and document to install vscode types separately (#21764)

Closes It still leads to conflicts due to double installation of vscode
types when testing through the cases, removing vscode types as
dependencies altogether and documenting to install it separately
instead.

Author: Kartik Raj

pythonExtensionApi/README.md

@@ -17,11 +17,14 @@ First we need to define a `package.json` for the extension that wants to use the
 	// Depend on the Python extension facade npm module to get easier API access to the
 	// core extension.
 	"dependencies": {
-		"@vscode/python-extension": "..."
+		"@vscode/python-extension": "...",
+        "@types/vscode": "..."
 	},
 }
 ```
 
+Update `"@types/vscode"` to [a recent version](https://code.visualstudio.com/updates/) of VS Code, say `"^1.81.0"` for VS Code version `"1.81"`, in case there are any conflicts.
+
 The actual source code to get the active environment to run some script could look like this:
 
 ```typescript

pythonExtensionApi/package-lock.json

@@ -25,9 +25,6 @@
     "bugs": {
         "url": "https://github.com/Microsoft/vscode-python/issues"
     },
-    "optionalDependencies": {
-        "@types/vscode": "^1.78.0"
-    },
     "devDependencies": {
         "typescript": "5.0.4",
         "@types/vscode": "^1.78.0"