[ws-manager-mk2] Enable tracing, add debug logs

[WVerlaek]

Description

• Enable tracing for ws-manager-mk2
• Add additional (debug) logging

Related Issue(s)

Part of #11416

How to test

View ws-manager-mk2 traces in EU jaeger instance. Deployed and tested from an ephemeral cluster

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

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

[kylos101]

@WVerlaek is a hold still needed? If yes, can you share why?

[WVerlaek]

@kylos101 yes - as it's a stacked PR

[kylos101]

@kylos101 yes - as it's a stacked PR

@WVerlaek 🤦 got it. Can you share a link to something describing the stack?

[WVerlaek]

@kylos101 it's these three PRs stacked in order:

• [ws-manager-mk2] Loadgen fixes, concurrent reconciliation #16613
• [ws-manager-mk2] Enable tracing, add debug logs #16643
• [ws-manager-mk2] Fix stopped status #16665

they're individual PRs of fixes discovered during loadtesting iterations, but stacked as during loadtesting it requires a build that contains the changes of all these PRs.