libva-v4l2-request-fourier-debian: route to debian-aarch64-bohr runner (#45)

Two follow-ups to PR #44 (which landed the libva-dev ABI pin):

- `051da5e` switch runs-on from arch-aarch64 → debian-aarch64-bohr
- `5feab57` fix runner label: actrunner-debian-aarch64-bohr (label name mismatch in 051da5e)

**Squash on merge** to keep main history clean.

Co-authored-by: Markus Fritsche <mfritsche@reauktion.de>
Reviewed-on: marfrit/marfrit-packages#45
Co-authored-by: Claude (noether) <claude@reauktion.de>
Co-committed-by: Claude (noether) <claude@reauktion.de>

debian/libva-v4l2-request-fourier/debian/changelog

@@ -1,6 +1,6 @@
 libva-v4l2-request-fourier (1.0.0+r378+gc332d34-2) bookworm trixie; urgency=medium
 
-  * Rebuild on a native Debian trixie runner (debian-aarch64-bohr) so
+  * Rebuild on a native Debian trixie runner (actrunner-debian-aarch64-bohr) so
     the driver picks up trixie's libva-dev (2.22) and exports
     __vaDriverInit_1_22 — the symbol trixie's libva runtime looks up.
     Previous -1 build used the Arch CI runner (libva 2.23.0) and
@@ -9,7 +9,7 @@ libva-v4l2-request-fourier (1.0.0+r378+gc332d34-2) bookworm trixie; urgency=medi
     and ffmpeg -hwaccel vaapi fails on startup.
   * No source change; pure build-env fix.  CI workflow's
     libva-v4l2-request-fourier-debian job moved from runs-on:
-    arch-aarch64 to runs-on: debian-aarch64-bohr; build-deps installed
+    arch-aarch64 to runs-on: actrunner-debian-aarch64-bohr; build-deps installed
     via apt-get instead of pacman.
   * Hard sanity check kept in build-deb.sh: build fails if the
     resulting .so doesn't export __vaDriverInit_1_22 (preempts the