Synced from Eclipse Che issue

https://github.com/eclipse/che/issues/21813

Describe the bug

Sometimes, when the user starts a new DevWorkspace, VS Code tries to restore its state. It looks odd to the user as the DevWorkspace is newly created so there must be no previous state.

It has a bad effect on the overall UX. For example:

• VS Code may show an errors that some files couldn't be reopened because they don't exist;
• Command Palette may contain some recently running Tasks that the user has never executed;
• VS Code doesn't suggest the user install the recommended extensions;
• etc.

Che version

next (development version)

Steps to reproduce

1. Start a new DevWorkspace with some project.
2. Try to open a few files and run some Tasks.
3. When you restart your DevWorkspace, VS Code will store its state (e.g. reopen the files) which is expected.
4. Remove the DevWorkspace.
5. Start a new DevWorkspace with a completely different project that has the same name as the previous one.
6. VS Code shows an error that it can’t find the files to reopen. In the Command Palette, some Tasks are shown as recently running.

Expected behavior

The state of the VS Code Workspace should be restored across restarts of the same DevWorkspace only. Even if it's named the same as some previously deleted ones.

Runtime

OpenShift

Screenshots

No response

Installation method

OperatorHub

Environment

Linux

Release Notes Text

When starting a new workspace VS Code may restore the state of a previous workspace showing commands and files that do not exist in the new workspace.