Add ability to configure borders in quick pick items list on plugin side

[vzhukovs]

What does this PR do?

This changes proposal align behavior to select target container when new terminal opens or new task starts. By the design the flow from the Find command action was taken. To separate developer and tooling containers:

When Find command is executed:

When new terminal opens:

When new task starts:

Devfile to test changes: https://gist.github.com/vzhukovskii/23b275d18af208629648430df251a78e/raw/6451e1d0589cb435bf58208d560fb8006e338cd8/che-dev-workspace.yaml

Steps to test changes manually:

• clone [che-theia](https://github.com/eclipse/che-theia) and theia
• checkout to quick_pick_items_ext in che-theia and theia repo
• build che-theia, then go to dockerfile/theia and build docker image: ./build.sh --build-args:GITHUB_TOKEN=${GITHUB_TOKEN},THEIA_VERSION=master --tag:next --branch:quick_pick_items_ext --git-ref:refs\\/heads\\/quick_pick_items_ext --skip-tests
• use built docker image eclipse/che-theia:next as image for the main editor in che.

Signed-off-by: Vlad Zhukovskyi vzhukovs@redhat.com

What issues does this PR fix or reference?

eclipse-che/che#13390

Release Notes

Add ability to configure borders in quick pick items list on plugin side

Docs PR

[RomanNikitenko]

@vzhukovskii
I get list of containers with group label if I have both: Developer and Tooling containers

but I get list of containers without group label if I have only Tooling containers for example.

Is it expected behavior?

[vzhukovs]

@RomanNikitenko yes, it's expected behavior

[AndrienkoAleksandr]

!container.attributes is better because cover null check, but up to you.

[AndrienkoAleksandr]

Looks like happy tests should be reworked by qa, because UI changed.

[RomanNikitenko]

Tested, the list of containers with group label is displayed:

• at creating a new terminal
• at running a task if component is not defined in a configuration

The comment contains case when group label is not displayed for containers

[che-bot]

❌ E2E Happy path tests failed ❗

See Details

• Jenkins job

• test report

• logs and configs

• Happy path tests DevFile

• images:

name	link
che-theia	docker.io/maxura/che-theia:532
che-remote-plugin-node	docker.io/maxura/che-remote-plugin-node:532
che-remote-plugin-runner-java8	docker.io/maxura/che-remote-plugin-runner-java8:532
che-remote-plugin-kubernetes-tooling-1.0.0	docker.io/maxura/che-remote-plugin-kubernetes-tooling-1.0.0:532

Tested with Eclipse Che Single User on K8S (minikube v1.1.1)

⚠️ https://github.com/orgs/eclipse/teams/eclipse-che-qa please check this report.

ℹ️ Use comment "crw-ci-test" to rerun happy path E2E test.

[musienko-maxim]

On this moment we have problem with PR check jobs, all steps from happy path was checked manually. The steps passed.