[gp-cli] provide workspace class info in top command

[mustard-mh]

Description

Show workspace class info in gp top command, support --json flag

Related Issue(s)

Fixes #10572

How to test

• Open a workspace in preview env https://mustard-mh3cbcc192a7.preview.gitpod-dev.com
• Exec command gp top and gp top --json to see if workspace class displayed
• Switch prefer workspace class in settings
• Start another workspace to check if data changed (manually change server config to add new type)

Release Notes

[gp-cli] provide workspace class info in `gp top` command

Documentation

• https://github.com/gitpod-io/website/pull/2653

Werft options:

• /werft with-preview

[werft-gitpod-dev-com]

started the job as gitpod-build-mustard-mh-gp-cli-gp-command-to-10572.1 because the annotations in the pull request description changed
(with .werft/ from main)

[mustard-mh]

How can users know their workspace's limit(show in command? or in document)? How to ask if they want to upgrade their plan (when CPU/MEM is nearly full?)

i.e. g1-standard Up to 4 vCPU, 8GB memory, 30GB disk

 {
      "id": "g1-standard",
      "category": "GENERAL PURPOSE",
      "displayName": "Standard",
      "description": "Up to 4 vCPU, 8GB memory, 30GB disk"
}

[mustard-mh]

For comment #12338 (comment) above

cc @loujaybee @akosyakov

[akosyakov]

How to ask if they want to upgrade their plan (when CPU/MEM is nearly full?)

I don't think we need to ask. Maybe just add a link to the plan page for now? cc @loujaybee

[filiptronicek]

@filiptronicek In production, id default will display with Standard (old): Up to 6 vCPU, 12GB memory, 30GB disk. You can see all classes in cm server-config

Thanks for pointing this out, Huiwen. I am having some issues with the command you mentioned but I don't think it matters, it makes sense in how you implemented this.

[akosyakov]

@Furisto Could you review it please?

[mustard-mh]

Fource push to

• Fix workspaceClassInfo not exists ( try with previous commit and run go run main.go top in gitpod-cli folder will get it)
• Change json flag's description
• Change command option var name
• Remove Fatal in workspace info query

See diff here

[akosyakov]

suggestion (non-blocking): add an option to disable this

I think it is important for people to know why they have such limits. I don't see one line as a bloat.

[filiptronicek]

suggestion (non-blocking): add an option to disable this

I think it is important for people to know why they have such limits. I don't see one line as a bloat.

@akosyakov touché. I meant with it that I personally would not find this much useful, and a one-off command like mentioned in #10572 (comment).

[jenting]

LGTM

[akosyakov]

lgtm

[akosyakov]

@mustard-mh You can unhold it?

[mustard-mh]

/unhold

[mustard-mh]

@gitpod-io/engineering-webapp Could someone review this PR?