[ws-manager-mk2] Fix workspace container detection

[Furisto]

Description

Fix workspace container detection. Depends on #16413. Without working workspace container detection resource constraints will not be applied to the workspace container.

Related Issue(s)

n.a.

How to test

• Open workspace
• Perform common runtime tests

Release Notes

None

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

Publish Options

• /werft publish-to-npm
• /werft publish-to-jb-marketplace

Installer Options

• with-ee-license
• with-slow-database
• 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-fo-adv-4.2 because the annotations in the pull request description changed
(with .werft/ from main)

[kylos101]

/hold

until #16413 is merged