[ws-daemon] Finalise cgroup v2 switch

[csweichel]

Description

We've been running on cgroup v2 for a while now, and any Gitpod installation on cgroup v1 is indicative of a configuration issue. On cgroup v1 core functionality of Gitpod does not function.

This PR removes the last remnant of cgroupv1 support, and enforces cgroupv2 within ws-daemon.

How to test

Run on a cgroupv1 system and observe ws-daemon failing to start.

Release Notes

Run solely on cgroup v2 systems

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=workspace
  Valid options are all, workspace, webapp, ide, jetbrains, vscode, ssh

[csweichel]

/hold

[werft-gitpod-dev-com]

started the job as gitpod-build-cw-cgroupv2.2 because the annotations in the pull request description changed
(with .werft/ from main)

[csweichel]

/werft run

👍 started the job as gitpod-build-cw-cgroupv2.3
(with .werft/ from main)

[csweichel]

/hold cancel

[aledbf]

/hold cancel