Update VS Code Browser to 1.76.1

[filiptronicek]

Description

Update code to 1.76.1

Progress

• Update Insiders (https://github.com/gitpod-io/gitpod/blob/main/WORKSPACE.yaml)
• Update Stable (https://github.com/gitpod-io/gitpod/blob/main/install/installer/pkg/components/workspace/ide/constants.go)

How to test

• Switch to VS Code Browser Insiders in settings.
• Start a workspace.
• Test the following:
  • terminals are preserved and resized properly between window reloads
  • WebViews are working
  • extension host process: check language smartness and debugging
  • extension management (installing/uninstalling)
  • install the VIM extension to test web extensions
  • that user data is synced across workspaces as well as on workspace restarts, especially for extensions
    • extensions from .gitpod.yml are not installed as sync
    • extensions installed as sync are actually synced to all new workspaces
  • settings should not contain any mentions of MS telemetry
  • WebSockets and workers are properly proxied
    • diff editor should be operable
    • trigger reconnection with window.WebSocket.disconnectWorkspace(), check that old WebSockets are closed and new opened of the same amount
  • workspace specific commands should work, i.e. F1 → type Gitpod prefix
  • that a PR view is preloaded when opening a PR URL
  • test gp open and gp preview
  • test open in VS Code Desktop, check gp open and gp preview in task/user terminals
  • telemetry data is collected in Segment

Release Notes

NONE

Werft options:

• /werft with-preview
• /werft analytics=segment

[werft-gitpod-dev-com]

started the job as gitpod-build-ide-code-1.76.1.1 because the annotations in the pull request description changed
(with .werft/ from main)

[filiptronicek]

/gh run recreate-vm

Comment triggered a workflow run

Started workflow run: 4383209862

• recreate_vm: true

[filiptronicek]

/gh run recreate-vm

Comment triggered a workflow run

Started workflow run: 4398625843

• recreate_vm: true

[filiptronicek]

Warning: Segment does not work here, but I believe it's because of the change to use GitHub Actions. There shouldn't be any problems and we can test in staging

[mustard-mh]

lgtm