fix: make workspace restart more informative

[vitaliy-guliy]

What does this PR do?

• bumps to @eclipse-che/che-devworkspace-generator:7.86.0
• displays a reason of a failure when trying to restart the workspace from a local devfile
• allows to easily open the devfile by a notification button

What issues does this PR fix?

eclipse-che/che#22913

How to test this PR?

• create a repository with https://github.com/vitaliy-guliy/vscode-test-extension?editor-image=quay.io/che-incubator-pull-requests/che-code:pr-363-amd64
• install yaml extension
• open .devfile.yaml and make some invalid change. I usually add the container environment variable

      env:
        - name: test
          value: true

The yaml extension should underline true as one that has wrong type (considering devfile schema it should be string instead of boolean).

• run Eclipse Che: Restart Workspace from Local Devfile command and select the devfile
  ( if there is only one devfile in the project, you can press Enter several times to confirm the reload )

• at this step you should be warned with an explanation of the reason of failure

Does this PR contain changes that override default upstream Code-OSS behavior?

• the PR contains changes in the code folder (you can skip it if your changes are placed in a che extension )
• the corresponding items were added to the CHANGELOG.md file
• rules for automatic git rebase were added to the .rebase folder

[github-actions]

Click here to review and test in web IDE:

[github-actions]

Pull Request Dev image published:
👉 quay.io/che-incubator-pull-requests/che-code-dev:pr-363-dev-amd64

[github-actions]

Pull Request Dev image published:
👉 quay.io/che-incubator-pull-requests/che-code-dev:pr-363-dev-amd64

[github-actions]

Pull Request Dev image published:
👉 quay.io/che-incubator-pull-requests/che-code-dev:pr-363-dev-amd64

[github-actions]

Pull Request Dev image published:
👉 quay.io/che-incubator-pull-requests/che-code-dev:pr-363-dev-amd64

[github-actions]

Pull Request Dev image published:
👉 quay.io/che-incubator-pull-requests/che-code-dev:pr-363-dev-amd64

[github-actions]

Pull Request Che-Code image published:
👉 quay.io/che-incubator-pull-requests/che-code:pr-363-amd64

[RomanNikitenko]

please update yarn.lock file

[vitaliy-guliy]

done

[github-actions]

Pull Request Dev image published:
👉 quay.io/che-incubator-pull-requests/che-code-dev:pr-363-dev-amd64

[github-actions]

Pull Request Che-Code image published:
👉 quay.io/che-incubator-pull-requests/che-code:pr-363-amd64

[RomanNikitenko]

tested,
works as described in the PR description

[svor]

lgtm

[devstudio-release]

Build 3.15 :: code_3.x/1414: Console, Changes, Git Data

[devstudio-release]

Build 3.15 :: sync-to-downstream_3.x/6905: Console, Changes, Git Data

[devstudio-release]

Build 3.15 :: get-sources-rhpkg-container-build_3.x/6855: Console, Changes, Git Data

[devstudio-release]

Build 3.15 :: push-latest-container-to-quay_3.x/4667: Console, Changes, Git Data

[devstudio-release]

Build 3.15 :: get-sources-rhpkg-container-build_3.x/6855:

code : 3.x :: Build 61609548 : quay.io/devspaces/code-rhel8:3.15-1
SUCCESS; copied to quay; /DS_CI/push-latest-container-to-quay_3.x/4667 triggered

[devstudio-release]

Build 3.15 :: update-digests_3.x/6709: Console, Changes, Git Data

[devstudio-release]

Build 3.15 :: code_3.x/1414:

Upstream sync done; /DS_CI/sync-to-downstream_3.x/6905 triggered

[devstudio-release]

Build 3.15 :: operator-bundle_3.x/3080: Console, Changes, Git Data

[devstudio-release]

Build 3.15 :: sync-to-downstream_3.x/6907: Console, Changes, Git Data

[devstudio-release]

Build 3.15 :: get-sources-rhpkg-container-build_3.x/6857: Console, Changes, Git Data

[devstudio-release]

Build 3.15 :: get-sources-rhpkg-container-build_3.x/6857:

devspaces-operator-bundle : 3.x :: Failed in 61615147 : BREW:BUILD/STATUS:UNKNOWN
FAILURE:; copied to quay

[the-it-jaeger]

This change is great @vitaliy-guliy, thank you!

I found one edge case: If the ServiceAccount running the DevWorkspace Pod does not have the appropriate k8s Role (permissions), you still get ambiguous HTTP Request errors when trying to perform actions such as "Dev Spaces: Restart Workspace from Local Devfile."

I discovered this when I had to override the default ServiceAccount so I could apply a custom SecurityContextContstraing and some extra securityContext for a special container component that had to run as a non-random user.