build(web): update web mode deps (#6460)

- Update web mode dependencies so we can run in debug mode
- Update docs w/ info on how to fix these dependencies as they go stale
often. Otherwise we may not be able to run in debug mode.


---

- Treat all work as PUBLIC. Private `feature/x` branches will not be
squash-merged at release time.
- Your code changes must meet the guidelines in
[CONTRIBUTING.md](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
- License: I confirm that my contribution is made under the terms of the
Apache 2.0 license.

Signed-off-by: nkomonen-amazon <[email protected]>

Author: nkomonen-amazon

docs/web.md

@@ -16,7 +16,7 @@ You can run the Web mode implementation of the extension in the following ways.
 -   To see logs, using the Command Palette search: `Toggle Developer Tools`. Then go to the `Console` tab. In web mode VS Code seems to duplicate log messages, idk how to fix this.
 -   The difference between web mode and Node.js/desktop is that in web mode everything runs in browser environment so certain things like Node.js modules will **not** be available.
 
-## Running in an actual Browser
+## Running in an actual Browser (Recommended)
 
 The following steps will result in a Chrome window running with VS Code
 and the web version of the AWS Toolkit extension installed:
@@ -43,7 +43,7 @@ and the web version of the AWS Toolkit extension installed:
     const context = browser
     ```
 
-2. In the `Run & Debug` menu select the `Extension (Chrome)` option
+2. In the `Run & Debug` menu select the `Extension Web` option
 
 > Note: To stop the debug session, you need to click the read `Disconnect` button multiple times
 
@@ -62,6 +62,12 @@ do the following:
 
 Now when you run the extension in the browser it will do CORS checks.
 
+### Troubleshooting
+
+-   `Extension Web` fails to launch
+    -   Update `@vscode/test-web` by running `$ npm install @vscode/test-web@latest`
+    -   Update/install playwright with `$ npx playwright install`. This will be mentioned in one of the build tasks outputs.
+
 ## Running in [vscode.dev](https://vscode.dev)
 
 The following will explain how to get your latest local development changes running in the actual `vscode.dev`. Use this if you want to test on an actual VS Code Web instance.

package-lock.json

@@ -51,7 +51,7 @@
         "@typescript-eslint/parser": "^7.14.1",
         "@vscode/codicons": "^0.0.33",
         "@vscode/test-electron": "^2.3.8",
-        "@vscode/test-web": "^0.0.54",
+        "@vscode/test-web": "^0.0.65",
         "@vscode/vsce": "^2.19.0",
         "eslint": "^8.56.0",
         "eslint-config-prettier": "^9.1.0",