Test shared process running as utility process

[bpasero]

Refs: #154050

• macOS @meganrogge
• linux @rzhao271
• windows @chrmarti

Complexity: 4

Create Issue

---

Enable window.experimental.sharedProcessUseUtilityProcess setting and restart to run the shared process in a utility process (and not in a hidden browser window). Verify the shared process runs as utility process via the process explorer. Hovering over shared-process you should see the kind being utility:

Do exploratory smoke testing of functionality that runs through the shared process:

• extension management (install, uninstall, update)
• you get extensions recommended in workspaces that configure it (e.g. vscode repo)
• language packs can install and language can be switched
• settings sync works
• you can open, use and close integrated terminals

Ensure there are no stray shared processes hanging around when you quit VS Code or kill it.