Feature Request: Add MUSL static binary in release process

[michael-burt]

Is your feature request related to a problem? Please describe.
The static binaries built as part of the release process depend on GLIBC 2.39. This is only supported on new Ubuntu systems (24+). Ubuntu 22 is an LTS release that is supported through June 2027, but the weaver static binaries produced as part of the release process do not work in these environments.

Describe the solution you'd like
I would like to add a musl binary to the release process that will work properly on old systems.

Describe alternatives you've considered
An alternative is to download the docker image and use that instead, but this is not always possible. Another option is to fork the project and build a binary compatible with older systems, but given the fact that Ubuntu 22 is an LTS release I think a musl binary should be built as part of this project.

_{Tip: React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.}

[jsuereth]

We could do with someone who wanted to help us with release management.

For context we're using cargo-dist so adding new targets shouldn't be too bad, just add them to our cargo config - https://axodotdev.github.io/cargo-dist/book/reference/concepts.html#defining-your-artifacts

And here's our config file: https://github.com/open-telemetry/weaver/blob/main/dist-workspace.toml#L12

Adding just MUSL should be relatively easy addition.

[nimishgj]

Submitted a fix for this in #1096. Added both x86_64 and aarch64 MUSL targets.