feat: Provide cwd for che terminal creation

[RomanNikitenko]

What does this PR do?

Provides current working directory for a terminal creation when user uses New Terminal (Select a container) action:

• value of the PROJECTS_ROOT env variable if there is no any workspace folder
• path to a folder if there is only one workspace folder
• IDE proposes user to select a folder if there is more then 1 workspace folder

What issues does this PR fix?

eclipse-che/che#23022

How to test this PR?

Empty workspace use case

• Go to the dashboard => Create Workspace page
• Use an Editor Definition => Editor Image => set quay.io/che-incubator-pull-requests/che-code:pr-384-amd64
• Select Empty Workspace to start a workspace
• main menu => Terminal => New Terminal (Select a container)
• check that /projects is used as a current working directory: type pwd for example in the created terminal

Workspace contains only one workspace folder

• Go to the dashboard =>Create Workspace page
• Use an Editor Definition => Editor Image => set quay.io/che-incubator-pull-requests/che-code:pr-384-amd64
• Select any sample to start a workspace
• main menu => Terminal => New Terminal (Select a container)
• check that project path is used as a current working directory: type pwd for example in the created terminal

Workspace contains more then one workspace folder

• Go to the dashboard =>Create Workspace page
• Git repo URL => set https://github.com/RomanNikitenko/web-nodejs-sample/tree/test-two-projects
• main menu => Terminal => New Terminal (Select a container)
• Select any folder when IDE proposes it
• check that selected path is used as a current working directory: type pwd for example in the created terminal

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

==========================================
Signed-off-by: Roman Nikitenko [email protected]

rh-pre-commit.version: 2.2.0
rh-pre-commit.check-secrets: ENABLED

[github-actions]

Click here to review and test in web IDE:

[github-actions]

Pull Request images published ✨

Editor: quay.io/che-incubator-pull-requests/che-code:pr-384-amd64
Dev image: quay.io/che-incubator-pull-requests/che-code-dev:pr-384-dev-amd64

[github-actions]

Pull Request images published ✨

Editor: quay.io/che-incubator-pull-requests/che-code:pr-384-amd64
Dev image: quay.io/che-incubator-pull-requests/che-code-dev:pr-384-dev-amd64

[vitaliy-guliy]

I have just tested the behavior for the described cases and can confirm the improvement works as expected.

Only one thing I would fix in the next PR is that if you clicked the New Terminal (Select a Container) menu item you are proposed to select a working directory. It is confusing a bit.

So if we have only one container, I would change the menu item title to New Terminal in a Container or New Terminal in a Tooling Container or something like that.

[RomanNikitenko]

@vitaliy-guliy
thank you for review and testing my changes!

about

if we have only one container, I would change the menu item title to New Terminal in a Container or New Terminal in a Tooling Container or something like that.

Thanks for your idea for the improvement!
I checked what we can do with it and see that:

• currently the title is placed on the VS Code browser side
• info about available containers is available on the che-extension side
• we should think about localization as well - as we have request for adding it from users

So - currently I don't see some easy way to implement it, probably we could find more suitable name for the command...

[github-actions]

Pull Request images published ✨

Editor: quay.io/che-incubator-pull-requests/che-code:pr-384-amd64
Dev image: quay.io/che-incubator-pull-requests/che-code-dev:pr-384-dev-amd64