meson: update to 1.10.1.

[CosmicToast]

Testing the changes

• I tested the changes in this PR: YES

Local build testing

• I built this PR locally for these architectures (if supported. mark crossbuilds):
  • x86_64-musl
  • aarch64-musl (cross)

[ahesford]

Meson is a significant package used in the build process of several others. Please test it more extensively than "briefly" before submitting an update.

[CosmicToast]

Please see my other comment for what "briefly" means in this context. When I next have some time I'll build a few non-trivial packages with it just to make sure (I typically prefer using muon but it isn't always compatible, so my usage of meson is slightly less regular; about weekly).

[CosmicToast]

To be more thorough with testing, as requested, I hand-built some non-trivial packages (making sure tests pass on my native architecture) with the bumped meson version, notably:

• dbus 1.16.2
• dav1d 1.5.3
• fcft 3.3.3
• fuse 3.18.1 (without running tests since those are python-only and I didn't feel like installing the handbuilt fuse)
• harfbuzz 12.3.1
• wayland 1.24.0

Hopefully this is enough to satisfy. In case questions come up as to the selection, here is how I picked the above packages:

1. In a void-packages checkout, I ran rg -l build_style=meson to list packages whose build_style is meson.
2. I browsed through the listing, picking out items that both would be relatively representative, but wouldn't be to huge a pain to build (e.g. not require installing too much).
3. I downloaded the latest release for each into ~/.local/src and built/tested them via meson setup build; samu -C build; samu -C build test.

Do let me know if you find the methodology to be insufficient, though I'm still not sure what is expected to break on a minor release that wouldn't be caught in tests or the binary not running properly in the first place.