Decouple gitpod web extension

[jeanp413]

Description

Decouple gitpod web extension

How to test

1. Open workspace and check gitpod-web extension is activated

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

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-jp-decouple-gitpod-web.7 because the annotations in the pull request description changed
(with .werft/ from main)

[jeanp413]

/werft run with-clean-slate-deployment

👍 started the job as gitpod-build-jp-decouple-gitpod-web.14
(with .werft/ from main)

[jeanp413]

/werft run

👍 started the job as gitpod-build-jp-decouple-gitpod-web.19
(with .werft/ from main)

[jeanp413]

/hold

[akosyakov]

We need to think how we are going to rollout. Could there be some issues with race conditions, ie some start a workpace but ide service does not resolve yet new images?

[mustard-mh]

Addressed #16073 (comment), and tested, going to add new iam in GCP

[mustard-mh]

We need to think how we are going to rollout. Could there be some issues with race conditions, ie some start a workpace but ide service does not resolve yet new images?

@akosyakov We have no race conditions, as this value is constant for all commits, ide-service only will return with the previous value of the latest value, and they are both correct (we will need to write compatibility code in gitpod-io/gitpod-code repo.

[akosyakov]

@mustard-mh for latest should be alright too?

[mustard-mh]

for latest should be alright too?

@akosyakov It will be a layer of image for both latest and stable browser code, so it (gitpod-web) will always be the one we configured in constants.go

[jeanp413]

There's errors in console, I remember seeing these before it's related to compilation I think, looking into it

cannot maintain connection to supervisor Error: 13 INTERNAL: Request message serialization failure: Expected argument of type supervisor.PortsStatusRequest 

[jeanp413]

/werft run

👍 started the job as gitpod-build-jp-decouple-gitpod-web.29
(with .werft/ from main)

[mustard-mh]

There's errors in console, I remember seeing these before it's related to compilation I think, looking into it

cannot maintain connection to supervisor Error: 13 INTERNAL: Request message serialization failure: Expected argument of type supervisor.PortsStatusRequest 

Browser code in preview env is out of date, cherry-pick commits in gp-code/main may fix it (also include a fixing for loggedInUserID) cc @jeanp413

[jeanp413]

yeah I missed the last commit in gitpod-shared fixing the bug in loggedInUserID also there was a bug in vscode compiling web release so had to rebase again 🤦

[jeanp413]

To fix for the serialization error I had to refactor a little bit gitpod-shared

[jeanp413]

/unhold