Release 0.11.2

[Milky2018]

Three fixes have landed since the 0.11.1 publish and none of them are reachable from the registry yet:

• Put the AArch64 branch-range fallback on the path the JIT compiles through (#486) #493 — the AArch64 branch-range fallback now sits on the path the JIT actually compiles through, so a function whose conditional branch exceeds imm19 compiles instead of failing (GitHub Wasm frontend threads every local through each control merge, causing AArch64 code-size explosion #486). wasmoon run also reports why the JIT refused a module instead of logging a bare string.
• Walk graphs with explicit stacks, not native recursion (ISS-401) #492 — recursive CFG and e-graph walks replaced with explicit stacks, fixing the wasm-gc stack overflow on deep graphs (ISS-401).
• Update moonbitlang/x to 0.4.48 and move off its deprecated env API #491 — off the deprecated @sys environment API onto moonbitlang/core/env, and moonbitlang/x to 0.4.48.

Why this bump is wide

machv and milkir both carry source changes, so every module pinning them has to re-pin to reach the fix. 0.11.1 was a three-module release; this one touches everything except regalloc and wasm_core, which are untouched and keep their versions.

module		module
machv	0.7.0 → 0.7.1	wasm_machv	0.4.0 → 0.4.1
milkir	0.5.0 → 0.5.1	x64_target	0.4.0 → 0.4.1
machv_regalloc	0.5.0 → 0.5.1	aarch64_target	0.5.1 → 0.5.2
milkir_machv	0.6.0 → 0.6.1	wasmoon_jit	0.6.1 → 0.6.2
wasm_milkir	0.5.0 → 0.5.1	wasmoon	0.11.1 → 0.11.2

Verification

• Workspace 2634/2634 native, 1028/1028 wasm-gc.
• moon check clean from a cold moon clean.
• WAST corpus 258/258 files, 62563 assertions, interpreter and JIT.
• Built binary reports 0.11.2.

Publishing to mooncakes.io follows once this merges.