Bump binfmt qemu image to v10.2.3
What does this MR do and why?
Bumps the binfmt emulator image from tonistiigi/binfmt:qemu-v10.0.4 to qemu-v10.2.3.
qemu 10.0.x mistranslates the guest's O_NOFOLLOW flag as O_LARGEFILE in openat2() (qemu-project/qemu#3262 (closed)). Ubuntu 24.04's GNU tar 1.35 creates every extracted file through openat2(), so tarball extraction breaks under arm64 emulation. This first surfaced as Cannot open: Invalid argument while extracting jemalloc in install-ruby on the workspaces multi-arch MR.
Credit to @miguel.sacristan1, who diagnosed the failure, reproduced it locally across qemu 9.2.2, 10.0.4, 10.1.3 and 10.2.1, and verified v10.2.3 fixes it in !1195 (merged) (repro details in this thread).
This is split out of !1195 (merged) so the emulator bump is validated and merged independently of the workspaces multi-arch work: the bug affects any emulated arm64 build extracting tarballs with a new enough tar, not just the workspaces image. Once this merges, !1195 (merged) can rebase and drop its qemu.yml change.
Validation
Changing .gitlab/ci/qemu.yml triggers every arm64-capable image job in this MR's pipeline (the changes: rules in .gitlab/ci/definitions.yml), so the pipeline itself is the regression check that all existing arm64 images still build under qemu v10.2.3.