* ci: share the musl Rust target setup as a composite action
Three container workflows carried the same toolchain, musl-tools and
aws-lc-sys link shim block verbatim.
* release: ship weed-worker as a static musl binary
The gnu build inherits the runner's glibc, 2.39 since the move to
ubuntu-24.04, so the released worker failed to start on Ubuntu 22.04
with 'GLIBC_2.38 not found'. The container images already build it
against musl with the same recipe.
* release: ship the Linux weed-volume as a static musl binary
Same glibc trap as the worker. The arm64 job also installed libssl,
which nothing in the volume links.
* ci: resolve the manual latest build's actions from master
Its checkout is an arbitrary source ref that may predate a local
action; the workflow itself always runs from master.
Chris Lu
42b6bc3d26