[tests] fix werft triggered workspace integration tests

[kylos101]

Description

The integration tests are optimized to run in werft. They stopped working this week. We are migrating to Github Actions in #16904, but, it is not stable yet.

This fixed werft, and unblocks our ability to deploy with certainty / makes it less likely that we'll introduce regressions to production. These tests are cross cutting, and use components from other teams (webapp and IDE).

Related Issue(s)

Fixes # n/a

How to test

1. assert we cant trigger tests, like so:

werft run github -j ./.werft/workspace-run-integration-tests.yaml \
-a with-integration-tests=workspace \
-a with-large-vm=true \
-a with-gce-vm=true \
-a with-werft=true

2. observe we have two broken tests! 😬:

--- FAIL: TestGitHubContexts/context/should_run_context_tests/github.com/atduarte/lfs-test_classic (110.02s)
--- FAIL: TestOpenWorkspaceFromOutdatedPrebuild/prebuild/it_should_open_a_workspace_from_with_an_older_prebuild_initializer_successfully_and_run_the_init_task/classic (19.42s)

Broke tests to be fixed in a follow-on PR.

3. assert preview environments (GCE preferred) still work, by browsing to the one for this branch
   • given this action - https://github.com/gitpod-io/gitpod/actions/runs/4451133728
   • https://kylos101-d6f6cc82c92.preview.gitpod-dev.com/workspaces was built
   • ran dazzle in https://gitpodio-dazzle-wo38jy0lq01.ws-dev.kylos101-d6f6cc82c92.preview.gitpod-dev.com/

Release Notes

NONE

Documentation

Build Options:

• /werft with-werft
  Run the build with werft instead of GHA
• leeway-no-cache
• /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-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-kylos101-debug-wks-integ.3 because the annotations in the pull request description changed
(with .werft/ from main)

[werft-gitpod-dev-com]

started the job as gitpod-build-kylos101-debug-wks-integ.4 because the annotations in the pull request description changed
(with .werft/ from main)

[werft-gitpod-dev-com]

started the job as gitpod-build-kylos101-debug-wks-integ.5 because the annotations in the pull request description changed
(with .werft/ from main)

[werft-gitpod-dev-com]

started the job as gitpod-build-kylos101-debug-wks-integ.6 because the annotations in the pull request description changed
(with .werft/ from main)

[kylos101]

/hold

to assert that the GCE preview environment works. it's building/creating now.

[kylos101]

/unhold
preview environment works ✔️

[kylos101]

@vulkoingim @mads-hartmann is there anything else you'd recommend I test as part of this change?