[gp-cli] Display the Gitpod Task ID instead of the Working Directory of the running task

[felladrin]

Description

Display the Gitpod Task ID instead of the Working Directory of the running task, on the list from gp tasks attach command.

To avoid confusion when more than two tasks are running in the same directory and haven't been named on .gitpod.yml.

Taking Phaser's .gitpod.yml config as example, which contains two tasks without the name property set:

tasks:
  - init: >
            npm install &&
            npm run build
    command: npm run watch
  - init: >
            cd ../ &&
            git clone https://github.com/photonstorm/phaser3-examples.git &&
            cd phaser3-examples &&
            npm install && npm start

When user opens Phaser's repo now, the terminal shows:

This PR changes it to be displayed as the following:

Here's how terminal names are displayed on VS Code Terminal now:

And gp tasks lists output is displayed like this:

gitpod /workspace/phaser (master) $ gp tasks list
|             TERMINAL ID              |     NAME      |  STATE  |
|--------------------------------------|---------------|---------|
| fafe9af7-caf4-41f5-9998-3a713c24d4ed | Gitpod Task 1 | running |
| 62339a91-d078-4d92-9c7e-27c891a31867 | Gitpod Task 2 | running |

Related Issue(s)

None.

How to test

• Open any repository that contains two or more tasks that keep running on background after the workspace starts and don't have a task name defined in .gitpod.yml. For example: Phaser's repo
• Confirm if unamed tasks from .gitpod.yml are displayed as Gitpod Task <ID> when gp tasks attach is executed.
• Note: gp tasks attach is executed automatically during the Welcome Message on JetBrains IDEs Terminals, that's what you see on the screenshots from the description of this PR.

Release Notes

The `gp tasks attach` command now shows the Gitpod Task ID instead of the working directory of the task, to avoid duplicated items in the list of running tasks, as most of the tasks runs in the root directory of the project.

Documentation

None.

[akosyakov]

lgtm

/hold

see a comment about VS Code integration, up to you to decide we can change it later too

[akosyakov]

lgtm

[akosyakov]

@felladrin feel free to deploy

[felladrin]

Thanks for reviewing it, @akosyakov!

/unhold