Update to .NET 10 build images

[sbomer]

This updates the libc requirement to:

• glibc 2.27
• musl libc 1.2.3

These images have LLVM 19.

Contributes to #109939

[dotnet-policy-service]

Tagging subscribers to this area: @dotnet/area-infrastructure-libraries
See info in area-owners.md if you want to be subscribed.

[jkoritzinsky]

Looks like there's some issues with the ARM32 images with zlib-ng, in particular around intrinsics.

Other than that, this looks good to me.

[sbomer]

The update to clang-19 includes support for neon intrinsics on arm32. However, the cmake check for NEON_HAS_LD4 in zlib-ng is failing. The check uses CMAKE_REQUIRED_FLAGS to pass -mfpu=neon, but this gets overridden settings in our toolchain.cmake (which passes -mfpu=vfpv3 via add_compile_options). This failed check results in a downstream compilation error (we attempt to compile https://github.com/zlib-ng/zlib-ng/blob/43d74a223b30902b44b01bf4c4888d8deb35e253/arch/arm/neon_intrins.h#L36-L38 in an environment that already provides the ld4 intrinsics).

We could fix this by changing our toolchain.cmake to pass -mfpu=vfpv3 via CMAKE_C_FLAGS and CMAKE_CXX_FLAGS instead of add_compile_options, which would let the CMAKE_REQUIRED_FLAGS setting take precedence. It might also be possible to fix the check in zlib-ng. zlib-ng/zlib-ng#1281 attempted to address a similar problem. Overall the pattern of setting compiler options in a toolchain doesn't work so well with compiler checks that try to set their own flags.

We decided to just disable neon for now, matching the .NET 9 configuration. Thanks for the help investigating this @jkoritzinsky!

[am11]

alpine arm32 build fixes: main...am11:runtime:feature/native/build-fixes

[sbomer]

Thanks @am11!