[ws-manager-mk2] include nodeName on failure

[kylos101]

Description

Include the node name, if available, in workspace failed log entries. This'll help us more easily determine if a single node is poisoned, or if the problem is more wide spread.

Related Issue(s)

Related to https://gitpod.slack.com/archives/C01TNS8EVQT/p1727709074376869

How to test

Try starting a workspace, kill registry-facade while the image is pulling:

Observe the log entry contains a node name:

Documentation

Preview status

Gitpod was successfully deployed to your preview environment.

• 🏷️ Name - kylos101-nodename
• 🔗 URL - kylos101-nodename.preview.gitpod-dev.com/workspaces.
• 📚 Documentation - See our internal documentation for information on how to interact with your preview environment.
• 📦 Version - kylos101-nodename-gha.29226
• 🗒️ Logs - GCP Logs Explorer

Build Options

Build

• /werft with-werft
  Run the build with werft instead of GHA
• leeway-no-cache
• /werft no-test
  Run Leeway with --dont-test

Publish

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

Installer

• analytics=segment
• with-dedicated-emulation
• workspace-feature-flags
  Add desired feature flags to the end of the line above, space separated

Preview Environment / Integration Tests

• /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 preemptible
  Saves cost. Untick this only if you're really sure you need a non-preemtible machine.
• with-integration-tests=all
  Valid options are all, workspace, webapp, ide, jetbrains, vscode, ssh. If enabled, with-preview and with-large-vm will be enabled.
• with-monitoring

/hold

[kylos101]

@nandajavarma can you add a ✅ ?

@geropl we should consider updating code owners.