VS Code data about a previously opened workspace is cached in the browser when switching workspaces

[cgruver]

Describe the bug

When switching workspaces, or deleting and re-creating a workspace, data from previously opened workspaces is still cached in the browser and used by VS Code.

See the below screenshot:

If I click on any of those links under Recent, I will get an error because those are reference to code-workspaces, files, and folders from other Che Workspaces.

Potentially related to: #22289

Che version

7.69

Steps to reproduce

1. Open a Che Workspace with VS Code as the editor (Don't know if IntelliJ is impacted)
2. Open files, folders, or a code-workspace
3. Close the Che Workspace
4. Open a different Che Workspace
5. Observe that the Recent list includes items from the closed Che Workspace.

Expected behavior

Cache is not retained after a workspace is closed.

Note: This expected behavior may also have negative UX impacts... There may be some level of caching needed for a good UX.

Perhaps, cache should be workspace unique, and deleted if a workspace is deleted...

Runtime

OpenShift

Screenshots

No response

Installation method

OperatorHub

Environment

macOS

Eclipse Che Logs

No response

Additional context

No response

[azatsarynnyy]

It looks like we're facing this problem again.
IIRC, previously, DevWorkspace ID was part of a workspace URL, so this solution worked well for Che. Now, the DevWorkspace's name is part of the URL instead, but not ID anymore, we need to adapt Che-Code to this change.

We have the DEVWORKSPACE_ID environment variable. But we can't read it directly from VS Code Core.
To fix this, we can try to pass DEVWORKSPACE_ID through the workbenchWebConfiguration from the backend to frontend to read it in the Workbench.