fix(checksum_updater): register binaryen/wrpc/wit-bindgen-wrpc; refresh bytecodealliance registries

[avrabe]

What

Found while checking bytecodealliance-tool versions: three tools were silently unregistered in tool_config.rs and fell through to create_default_config()'s repo guess — which is wrong for all three. Every update attempt failed with "Failed to get release for X".

tool	wrong guess	real repo
binaryen	bytecodealliance/binaryen	WebAssembly/binaryen
wrpc	bytecodealliance/wrpc-wasmtime	bytecodealliance/wrpc
wit-bindgen-wrpc	bytecodealliance/wit-bindgen-wrpc	bytecodealliance/wrpc (monorepo)

• binaryen: PerPlatformAsset, tag version_{version} (bare numeric, no v prefix) — matches tool_registry.bzl's existing binaryen entry.
• wrpc / wit-bindgen-wrpc: static per-platform binary names (no version embedded, matches filename: "{suffix}" / is_binary=True) — both dropped glibc-linux for musl-only and ship no native Windows MSVC (gnu .exe only) as of v0.16+, matching the existing hand-authored registry values, confirmed current at v0.17.0.

With the fix, refreshed the registry only (checksums/tools/*.json) for all 9 bytecodealliance/upstream tools:

wasm-tools  1.246.2 -> 1.254.0
wit-bindgen         -> 0.60.0   (registry tracking only — see note below)
wac         0.9.0   -> 0.10.1
wasmtime    45.0.1  -> 47.0.2
wkg         0.15.0  -> 0.16.0
wrpc / wit-bindgen-wrpc -> 0.17.0
binaryen    129     -> 131
wasi-sdk    32      -> 33

⚠️ Does NOT move any active build pin

toolchains/tool_versions.bzl is a separate, hand-maintained TOOL_VERSIONS dict that get_tool_version() actually reads — not the registry's latest_version. It intentionally holds some tools back (wit-bindgen is pinned at 0.55.0: "0.58 changes C codegen type names, breaks cpp_component"). This PR is purely a registry/checksum refresh; it does not change what gets built. Bumping the active pins (especially wasm-tools/wasmtime, tied together via TOOL_COMPATIBILITY_MATRIX) is a separate, higher-risk call requiring the compat-matrix + full-pipeline verification the file's own docs mandate — not done here.

Verification

• validate --tools <all 9> → 45/45 checksums valid (re-downloaded, recomputed).
• wasi-sdk's Windows platforms (arm64/amd64, ~650MB tarballs) hit a transient timeout on the first pass and were silently dropped from the written entry — caught it, retried, confirmed all 6 platforms present before committing.
• Restored the description field the serializer drops (wrpc, wit-bindgen-wrpc).
• Two new unit tests pin the corrected URLs (test_binaryen_was_unregistered_now_correct_repo, test_wrpc_and_wit_bindgen_wrpc_were_unregistered_now_correct_repo). Full lib suite 26/26 pass.

Deliberately not done

componentize-py stays unregistered — it's pinned to the rolling canary tag, and a versioned release (v0.25.0) now exists upstream, but switching off canary is a MODULE.bazel-level call, not the updater's to make silently. Flagged as a follow-up.

🤖 Generated with Claude Code