build-number

Build Windows ARM64 with cargo instead of cross needsCrossCompile had same-OS cases for apple and linux but not windows, so an x86_64 Windows host targeting aarch64-pc-windows-msvc fell through to the `host !== target` catch-all and picked cross, failing with "Failed to spawn 'cross': entity not found". Installing cross on the Windows agents would not have helped: it drives Linux Docker images and has no MSVC support at all. Windows ARM64 cross-compiles natively via the ARM64 MSVC tools, which the agents already have. Generalise the per-OS cases into an osFamily helper (android checked first, since its triples also match linux) so same-OS/different-arch consistently means cargo, and replace the catch-all with explicit routing. Combinations with no working toolchain, such as an Apple target from a non-Apple host, now throw up front rather than dispatching to a tool that cannot service them and failing later with a confusing error.