[ws-proxy] Distinguish between WS_NOTFOUND and WS_ID_INVALID

[iQQBot]

Description

[ws-proxy] Distinguish between WS_NOTFOUND and WS_ID_INVALID

We have too many metrics report with WS_NOTFOUND but, this WS_NOTFOUND is not really workspace not found, This also includes some attempts at external brute force hacking attacks, This PR tries to distinguish between brute force attempts and real workspace not found errors, at this point we are only looking at the workspaceID format

Related Issue(s)

Fixes #

How to test

1. start a workspace from this branch
2. run ./dev/preview/portforward-monitoring-satellite.sh -c harvester and open prometheus
3. test copy/paste ssh command, it should works
4. test ssh root@test.ssh.ws.pd-ssh-invalid-wsid.preview.gitpod-dev.com it will increase WS_ID_INVALID error
5. test ssh gitpodio-templategolang-uiuho6zqyss@test.ssh.ws.pd-ssh-invalid-wsid.preview.gitpod-dev.com it will increase WS_NOTFOUND error

prometheus query

gitpod_ws_proxy_ssh_attempt_total{status="failed", error_type=~"(WS_ID_INVALID|WS_NOTFOUND)"}

Release Notes

NONE

Documentation