chore(release): v0.41.2 — stale reloc.CODE backstop

[avrabe]

Cuts v0.41.2, shipping the #351 soundness backstop (#352, SR-53 verified).

• meld now hard-fails with MisalignedReloc when a reloc.CODE memory-address
  site does not land on a rebasable immediate (stale/drifted relocs from
  LEB-relaxation; upstream reloc.CODE offsets stale after LEB relaxation: +2/reloc drift desyncs reloc sites from emitted code (wit-component 0.245.1) wasm-tools#3), instead of silently
  miscompiling --memory shared --address-rebase output.
• avrabe confirmed the fix on a fresh build (meld --memory shared --address-rebase skips R_WASM_MEMORY_ADDR_SLEB relocations: a rebased module's i32.const data pointer stays stale -> silent cross-component aliasing (gap in #340) #351).
• rivet release status v0.41.2 → ✓ cuttable (1 artifact, verified).

Falsification: test_351_stale_reloc_offsets_hard_error.

Version bump 0.41.1 → 0.41.2; CHANGELOG rolled. Tag v0.41.2 cut on merge.

[github-actions]

LS-N verification gate

✅ 59/59 approved LS entries verified

	count
Passed (≥1 test, all green)	59
Failed (≥1 test failure)	0
Missing (no ls_*_NN_* test found)	0

_{Approved loss-scenarios.yaml entries are expected to have a
regression test named ls_<letter>_<num>_* (e.g. LS-A-11 →
ls_a_11_*). The gate runs each prefix via cargo test --lib --no-fail-fast and aggregates pass/fail/missing.}

Failed LS entries

(none)

Missing regression tests

(none)

_{Updated automatically by tools/post_verification_comment.py.
Source of truth: safety/stpa/loss-scenarios.yaml.}