[ws-manager] allow user custom closed timeout

[iQQBot]

Description

This PR introduces custom closed timeout, which allows users to customize closed timeout in user preference (need discuss only allow opt-out or can set to anytime)

workspace timeout means inactive timeout

This is the workspace part, it only contains

1. add SetTimeout props (type), which allow set workspace timeout or closed timeout, default is workspace timeout, so it's compatible with previous call methods, can be deployed separately
2. if the user change workspace timeout, it will automatic disabled closed timeout.
3. add closed_timeout in StartWorkspaceSpec.
4. if closed_timeout set to 0, it means we disabled check closed timeout
5. change timeout condition -> if workspace in closed status, check closed timeout, if not timeout, continue to check workspace timeout

Related Issue(s)

Relate #16089

How to test

1. open this branch in gitpod.io, wait preview environment context install.
2. open preview environment
3. change your bill to a paid plan, you can find test card in here
4. start a workspace in this preview environment, run gp timeout set 1h
5. run kubectl describe pods ws-{your-workspace-instance-id} in your step 1 workspace to check pod annotation. it should be like this.

              gitpod/customClosedTimeout: 0
              gitpod/customTimeout: 60m

6. close web ide, wait for 10m, and check workspace not timeout.
7. change timeout to 10m, and wait for 10m, make sure workspace timeout.

Release Notes

NONE

Documentation

Build Options:

• /werft with-github-actions
  Experimental feature to run the build with GitHub Actions (and not in Werft).
• leeway-no-cache
  leeway-target=components:all
• /werft no-test
  Run Leeway with --dont-test

Publish Options

• /werft publish-to-npm
• /werft publish-to-jb-marketplace

Installer Options

• with-ee-license
• with-slow-database
• with-dedicated-emulation
• with-ws-manager-mk2
• workspace-feature-flags
  Add desired feature flags to the end of the line above, space separated

Preview Environment Options:

• /werft with-local-preview
  If enabled this will build install/preview
• /werft with-preview
• /werft with-large-vm
• /werft with-gce-vm
  If enabled this will create the environment on GCE infra
• /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-pd-custom-close-timeout.4 because the annotations in the pull request description changed
(with .werft/ from main)

[iQQBot]

@WVerlaek I addressed your feedback, could you review it again? 🙏

[WVerlaek]

Changes lgtm, running some tests now. Do we have/get docs for this as well?