ci: dump context when job ends

[crazy-max]

- What I did

related to recent issues on ci when building: https://github.com/moby/moby/actions/runs/8571772790/job/23492886675?pr=47683#step:6:193

#5 docker-image://docker.io/docker/dockerfile:1.7@sha256:dbbd5e059e8a07ff7ea6233b213b36aa516b4c53c645f1817a4dd18b83cbea56
#5 resolve docker.io/docker/dockerfile:1.7@sha256:dbbd5e059e8a07ff7ea6233b213b36aa516b4c53c645f1817a4dd18b83cbea56 done
#5 sha256:ccef65a67ab38a038c615e74c797b11a43d36505710abe93c87b021401bebd81 11.98MB / 11.98MB 0.1s done
#5 extracting sha256:ccef65a67ab38a038c615e74c797b11a43d36505710abe93c87b021401bebd81 0.1s done
#5 DONE 0.2s
Dockerfile:1
--------------------
   1 | >>> # syntax=docker/dockerfile:1.7
   2 |     
   3 |     ARG GO_VERSION=1.21.9
--------------------
ERROR: failed to solve: fork/exec /usr/bin/buildkit-runc: exec format error

- How I did it

Adds Dump context step across our workflows to help debugging this issue. Also enable debug for builder.

- How to verify it

- Description for the changelog

- A picture of a cute animal (not mandatory but encouraged)