new(winehq.org): headless wine for Windows-binary CI testing

[tannevaled]

Closes #12985.

What

Adds a winehq.org recipe — a minimal headless build of Wine sufficient to run console-only Windows binaries on a Linux host. Pilot scope: linux/x86-64 only.

Why

Unblocks #12984 (llvm.org/mingw-w64) — that recipe's test step is already wired with a soft-dep on winehq.org, so once this lands the cross-compile pilot upgrades from "PE magic-byte check" to "actually run the .exe and assert stdout". More broadly: any future Windows-targeting pantry recipe gets real runtime tests in the existing Linux CI infra (no GitHub Windows runners needed).

Architecture context: pkgxdev/brewkit#346 RFC.

Build configuration

Stripped down to the minimum needed for CLI tool execution:

Flag	Why
--enable-archs=x86_64	64-bit only — halves build, sufficient for our use
--disable-tests	skip wine's massive internal test suite
--without-x	no X11 in CI
--without-opengl --without-osmesa --without-vulkan	no 3D
--without-alsa --without-pulse --without-oss	no audio
--without-sdl --without-gstreamer	no multimedia
--without-cups --without-gphoto --without-usb --without-v4l2 --without-sane --without-udev --without-pcap	no peripherals
--without-fontconfig --without-krb5 --without-capi --without-cms	other unneeded subsystems

Build deps from pantry: gnu.org/bison, github.com/westes/flex, perl.org, gnu.org/gettext, freetype.org, gnutls.org, zlib.net, plus the toolchain (gnu.org/{make,gcc,binutils}).

Test

wine64 --version   # expects "wine-X.Y"

That's all. Anything more substantive belongs in consumer recipes (e.g., llvm-mingw runs hello.exe through wine).

Limitations / future work

• linux/aarch64 — wine can run aarch64 Windows binaries on aarch64 Linux, but x86-64 Windows binaries need qemu-user or Hangover. Out of scope for pilot.
• darwin — wine 11.x ships macOS support but configuration is meaningfully different (32-bit deprecation dance). Follow-up.
• wine-staging — we pick the stable branch; staging is generally OK too but adds churn.
• MinGW-built Wine — --with-mingw produces wine with better Windows compat for the win-side DLLs, but requires a Linux-hosted mingw toolchain present at wine build time (which we now have via new(llvm.org/mingw-w64): LLVM-based mingw-w64 cross-compiler (Windows-target toolchain) #12984). Possible follow-up to unlock harder-to-emulate APIs.

Test plan

• CI green on linux/x86-64
• wine64 --version returns wine-11.0 (or whatever stable is at build time)
• As consumer-side validation: new(llvm.org/mingw-w64): LLVM-based mingw-w64 cross-compiler (Windows-target toolchain) #12984's test step runs hello.exe through this wine when both PRs are merged

Refs: #12985 (this issue), pkgxdev/brewkit#346 (Windows port RFC), pkgxdev/pkgx#607 (platform megaticket).

[tannevaled]

Round 3 finding: wine is also blocked on #12968.

--without-mingw doesn't fully disable the cross-compiler requirement — --enable-archs=x86_64 still triggers wine's configure to look for an x86_64 PE compiler:

configure: error: x86_64 PE cross-compiler not found.
This is an error since --enable-archs=x86_64 was requested.

That makes sense: wine MUST build its own Windows-side DLLs (kernel32, ntdll, …) for the requested target arch, because those DLLs interpose Windows API calls into Linux syscalls. There's no "ship without Windows-side DLLs" path.

So wine builds need a mingw cross-compiler. Adding llvm.org/mingw-w64 as a build dep would normally fix this — but:

pkgxdev/pantry#12968  (glibc, approved/awaiting merge)
       │
       │ (unblocks)
       ▼
pkgxdev/pantry#12984  (llvm-mingw, currently can't run clang)
       │
       │ (build dep)
       ▼
THIS PR (wine)

So this PR's full unblock chain is #12968 → #12984 → this.

For now: leaving the recipe with the current --enable-archs=x86_64 + --without-mingw combo. Once #12984 becomes buildable I'll add it as a build dep and the configure should pass.

(Side note: --without-mingw does prevent wine from REQUIRING mingw post-configure, but it doesn't override --enable-archs's implicit PE-compiler requirement. Wine's configure has both knobs but --enable-archs is the stronger one.)