Jwt-proxy is displayed as machine on IDE UI

[Ohrimenko1988]

Description

In this PR (#10463) @mshaposhnik add a "jwt-proxy" functionality.
The problem is the "jwt-proxy" displays as the machine in the workspace. It leads to regression (almost 20 %) in the tests which oriented to the using of the workspace with a single machine and unexpected machine selection dialog causes the fails:

Besides it looks veard for user which expects single machine in his workspace. And as @sleshchenko wrote in the ##10463 the "jwt-proxy" doesn't have terminal, or exec-agent servers. @vparfonov could you clarify this issue?

Test report with reproduced bug:
https://ci.codenvycorp.com/job/che-pullrequests-test-ocp/505/Selenium_20tests_20report/

[ghost]

We should probably mark/tag such machines somehow, so that clients can filter machines accordingly.

[skabashnyuk]

I don't think this is a bug either

[sleshchenko]

@skabashnyuk Could you elaborate why do you think so? How is it possible to execute a command in a machine where exec server is not present?

@eivantsov Do you mean marking for hiding such machines at all? In the specific case, IDE can filter machines which don't have exec server.

[skabashnyuk]

@skabashnyuk Could you elaborate why do you think so? How is it possible to execute a command in a machine where exec server is not present?

We will figure out that with Theia based ide.
My point: we should not spend much time with new components with GWT based IDE.

[sleshchenko]

@skabashnyuk

we should not spend much time with new components with GWT based IDE.

Good point. I don't think that it changes the kind of issue but I agree with you about it.
I don't think that it requires a lot of time to fix this issue.

BTW It is not a critical issue since jwtproxy is disabled by default but it would be fixed before enabling jwtproxy by default.

[skabashnyuk]

Ok. let's reformulate issue. Do not show machine without exec agent for the command execution target. WDYT?

[sleshchenko]

There is an issue for marking tooling machines with a special attribute #11804

[che-bot]

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.