Improve Gitpod timeouts for multiple clients (revise the 5 minute editor connection timeout)

[loujaybee]

Currently, a workspace will initiate a 5 minute timer from close of any active editor. This current behaviour assumes too much that the user is operating a single client connection. Gitpod should be smart enough to recognise when a user is making multiple connections and not time out when a user swaps between SSH, VS Code or JetBrains with a workspace.

However, in scenarios where there are two editors open, this timeout should not be triggered. Ideally, we initiate the timer from the last active editor, to prevent breaking workflows where two editors are used. We should also check: https://github.com/gitpod-io/website/issues/2144 - to ensure the timeout logic is fully documented.

See internal link [1]

[jeanp413]

I didn't know about the 2 minutes timeout and I've hit this multiple times lately while testing the SSH stuff in gitpod-desktop extension, and it was really annoying 😄

[loujaybee]

Associated with: https://github.com/gitpod-io/customers/issues/57

[loujaybee]

If this is purely a cost-saving mechanism, we could look to modify the behavior only for certain cohorts

e.g. customers on X plans, etc?