Display IDE detail versions

[mustard-mh]

Describe the behaviour you'd like

Display IDE detail versions, so that users know what Gitpod actually support now.

see also #7932 (comment)

[gtsiolis]

FWIW, now that we have a single array of browser and desktop options (see relevant comment) it's much easier to support this as:

1. We'll always know the VS Code version we use for the browser option for latest or not
2. We can use the Insiders label on the VS Code desktop option
3. We can use the EAP label on the JetBrains' desktop options

question: One question that's not clear to me yet, is whether we know exactly which JetBrains editor version we're using when using the latest or not. Cross referencing relevant comment.

[gtsiolis]

Re-posting from the relevant discussion (internal) (Cc @akosyakov) for visibility regarding the question mentioned above:

• We have CI jobs which keep stable and latest versions up-to-date in Gitpod and we provision these versions in workspaces. These CI jobs should be improved to capture info about concrete versions.
• JB Gateway while connecting to a workspace check which backend we are running and then provision a proper client to the local machine.

[gtsiolis]

Posting below an early draft how versions could suface on the editor options as well as how we could move the editor type form the bottom label to the top right corner with icon and a tooltip. Cc @mustard-mh @akosyakov

Early draft with editor versions and editor type tooltip

[akosyakov]

I like how versions displayed, but can we rather have VS Code Web and VS Code Desktop?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[gtsiolis]

Re-opening as this is still relevant.

[akosyakov]

We could put manifest file with version in first layer of IDE image under the same path and then use blobserve to resolve it in ide-service.

[gtsiolis]

Closing this as the first iteration has been added in #15139.

Follow-up issue and next iteration can be found in #15194.

Cc @filiptronicek @mustard-mh @akosyakov @easyCZ