[server, cli] Allow flexible workspace timeouts

[svenefftinge]

Description

Makes setWorkspaceTimout handle arbitrary poistive duration strings, matching the format <\D+[mhd]>, which is compatible with go's time Duration.

Related Issue(s)

Fixes #9038

How to test

• Verify that extending timouts still work as before
• try gp timeout set 4h

Release Notes

A new CLI command `gp timeout set` allows to set the workspace timeout to arbitrary durations.

Documentation

Build Options:

• /werft with-github-actions
  Experimental feature to run the build with GitHub Actions (and not in Werft).
• /werft with-local-preview
  If enabled this will build install/preview
• /werft with-preview
• /werft with-payment
• /werft with-large-vm
• /werft with-integration-tests=all
  Valid options are all, workspace, webapp, ide, jetbrains, vscode, ssh

[werft-gitpod-dev-com]

started the job as gitpod-build-se-allow-flexible-timeouts.1 because the annotations in the pull request description changed
(with .werft/ from main)

[werft-gitpod-dev-com]

started the job as gitpod-build-se-allow-flexible-timeouts.5 because the annotations in the pull request description changed
(with .werft/ from main)

[jldec]

Tested in preview

gitpod /workspace/readme (main) $ gp timeout show
Timeout for current workspace is 30m
gitpod /workspace/readme (main) $ gp timeout extend
Cannot extend workspace timeout for current plan, please upgrade your plan
## 
## had to add PAYG before being allowed to set timeout (this was expected)
## 
gitpod /workspace/readme (main) $ gp timeout set 180
jsonrpc2: code 650 message: Invalid duration : Invalid timeout unit: 0
gitpod /workspace/readme (main) $ gp help timeout  set
Set timeout of current workspace.

Duration must be in the format of <n>m (minutes), <n>h (hours), or <n>d (days).
For example, 30m, 1h, 2d, etc.

Usage:
  gp timeout set <duration> [flags]

Examples:
gitpod timeout set 1h

Flags:
  -h, --help   help for set

$ gp timeout show
Timeout for current workspace is 30m

$ gp timeout extend
Workspace timeout has been extended to three hours.

$ gp timeout set 300m
Workspace timeout has been set to 300m.

$ gp timeout set 5h
Workspace timeout has been set to 5h.

$ gp timeout show
Timeout for current workspace is 5h

It would be better if the response to gp timeout set and gp timeout show did not use the same input string as was entered via gp timeout set because this created uncertainty about whether the input was parsed correctly.

Suggested interaction

• consistent use of "n minutes" in responses (no period at the end)
• maybe simpler error messages

$ gp timeout set 300m
Workspace timeout has been set to 300 minutes

$ gp timeout show
Timeout for current workspace is 300 minutes

$ gp timeout set 5h
Workspace timeout has been set to 300 minutes

$ gp timeout show
Timeout for current workspace is 300 minutes

$ gp timeout set 1d
Workspace timeout has been set to 1440 minutes

$ gp timeout set 1d5h
Error: invalid duration "1d5h": time: unknown unit "d" in duration "1d5h"

[svenefftinge]

I've added the suggested changes.

[easyCZ]

/hold for review Qs

[easyCZ]

Code wise looks ok.

[svenefftinge]

/unhold

[akosyakov]

Code looks good, rely on @svenefftinge for testing. I did not try.

/hold

merge when you are ready 🚀

[svenefftinge]

/unhold