Toolkit can run in web browser (e.g. vscode.dev), avoid nodejs APIs

Toolkit currently doesn't support "web" version of vscode, https://vscode.dev


## Considerations

- https://code.visualstudio.com/blogs/2021/10/20/vscode-dev#_extensions
> For example, change `https://github.com/microsoft/vscode` to `https://vscode.dev/github.com/Microsoft/vscode`.
> If you are not on GitHub or Azure DevOps, support for additional repository hosting services can be provided through extensions, just like on the desktop.
- Need to avoid direct interaction (nodejs api) with the OS
- fileystem in favor the "virtual fs" (VFS) layer
- network ([use vscode api for http requests](https://github.com/aws/aws-toolkit-vscode/issues/3417#issuecomment-1536518807) instead)
- Could help with "minimum trust". #1823

## What can AWS Toolkit do with/without "compute"?

- **without** compute: we can make SDK calls and network requests, so features like these can work, in theory:
- AWS Explorer
- Language services (LSP, JSON-schema)
- **with** compute: we can use features that require a filesystem and operating system:
- SAM CLI
- Docker

Start with the VS Code web extension guidance linked in the issue, then map the toolkit’s direct Node.js and operating-system interactions. Separate features that can work without compute from those requiring SAM CLI, Docker, or a filesystem. Done means browser-compatible features use VS Code APIs and the virtual filesystem, with unsupported compute-dependent features clearly identified.

Written by the indexing model from the issue text.