Enhancement: add missing cross-compilation targets (armv7 hardfloat, aarch64 musl)

[chloe41427]

Missing Targets

The current release workflow builds for 6 targets, but several common platforms are missing:

Rust Triple	Platform	Use Case
armv7-unknown-linux-gnueabihf	linuxarm32hf	Raspberry Pi 2/3 (Raspbian 32-bit)
aarch64-unknown-linux-musl	linuxarm64musl	Alpine Linux on ARM64
armv7-unknown-linux-musleabihf	linuxarm32hfmusl	Alpine Linux on 32-bit ARM

All three are Rust Tier 2 targets with full std library support and are handled by taiki-e/setup-cross-toolchain-action.

Related Issues

• Bug: Failed to download native client for Raspbian sdkman-cli#1148 — native client 404 on Raspbian (linuxarm32hf binary missing)
• Bug: OpenJDK: Add Support for Alpine Linux sdkman-cli#1133 — Alpine Linux support (musl-based JDKs)

What needs to change

1. Add new matrix entries to the release.yml build workflow
2. Add platform replacements to jreleaser.yml
3. Add artifact entries to the distributions section of jreleaser.yml
4. Add MongoDB update entries to bin/release-binary.sh for the new platform identifiers

[aalmiray]

FWIW these are the current os/arch values supported by JReleaser when setting a value for the platform property of an artifact:

platform:
aix, hpux, os400, linux, linux_musl, osx, freebsd, openbsd, netbsd, sunos, windows, zos.

arch:
x86_64, x86_32, itanium_64, itanium_32, sparc_32, sparc_64, arm_32, aarch_64, mips_32, mipsel_32, mips_64, mipsel_64, ppc_32, ppcle_32, ppc_64, ppcle_64, s390_32, s390_64, riscv

https://jreleaser.org/guide/latest/concepts/artifacts.html

If there were to be no exact match for a given os-arch combination then please file a ticket at https://github.com/jreleaser/jreleaser/issues

As a workaround you can define any other os-arch combination as long as all artifacts have a different value.