Backport of container-stack for jammy, noble and questing

[Lena Voytek]

[Impact]

In order to follow our policy on keeping the container stack
(docker.io-app, containerd-app, runc, runc-app, docker-buildx, and
docker-compose-v2) up-to-date in our supported releases, let's backport
the stack in jammy, noble and questing to <target releases>.

[Test Plan]

Per https://wiki.ubuntu.com/DockerUpdates, our test case is the autopkgtests.

All packages were built in https://launchpad.net/~athos-ribeiro/+archive/ubuntu/container-stack-pp/+packages.

Apart from runc-app, all packages are failing their autopkgtest runs in our infrastructure due to the dockerhub pull rate limits. For those (docker.io-app, containerd-app, docker-buildx, and docker-compose-v2), we ran the autopkgtest suite locally. All tests are passing.

[Where problems could occur]

As usual, we deliver most benefit to our users by delivering an upstream experience. A risk of regressions is part of that.

[Past MREs]

- https://bugs.launchpad.net/ubuntu/+source/docker.io-app/+bug/2040461
- https://bugs.launchpad.net/ubuntu/+source/docker.io-app/+bug/2040460
- <Additional MREs>