chromium: Fixes for 142 and wrynose compatibility

[zboszor]

This contains most of of #962 without the upgrade to 144.
musl patches were updated for 142. They are also applicable through the 144, 145 and 146 upgrades.

[MaxIhlenfeldt]

lgtm, thanks!

[zboszor]

FWIW, the musl patches were checked to apply mostly cleanly (no fuzz) up to Chromium 146. But I have not tested to build Chromium for musl, only for glibc.

I have just run these commands to see the build and target triplets:

$ MACHINE=qemuarm64 bitbake -e chromium-x11 | grep -E 'RUST_(TARGET|BUILD)_SYS='
RUST_BUILD_SYS="x86_64-unknown-linux-gnu"
RUST_TARGET_SYS="aarch64-oe-linux-musl"
$ MACHINE=raspberrypi3 bitbake -e chromium-x11 | grep -E 'RUST_(TARGET|BUILD)_SYS='
RUST_BUILD_SYS="x86_64-unknown-linux-gnu"
RUST_TARGET_SYS="armv7-oe-linux-musleabihf"
$ MACHINE=intel-corei7-64 bitbake -e chromium-x11 | grep -E 'RUST_(TARGET|BUILD)_SYS='
RUST_BUILD_SYS="x86_64-unknown-linux-gnu"
RUST_TARGET_SYS="x86_64-oe-linux-musl"

Apparently, neither Chromium version will build for musl, because

• 0009-Adjust-the-Rust-build-to-our-needs.patch hardcodes gnu or gnueabihf and none of the musl patches changes that to musl or musleabihf
• The gni file responsible for setting the system triplet for a given CPU architecture to find libclang_rt.a does not really distinguish between the build and target, so e.g. a build host with glibc / x86_64 with the target build for musl / x86_64 won't be able to handle this.

I don't have any inclination to fix this. See also #580 as a failed / given up attempt.