chore: upgrade thorchain v3.15.2

[kaladinlight]

Summary by CodeRabbit

• Chores
  • Upgraded core node and smart-contract runtime dependencies to newer, compatible releases to improve stability, compatibility, and runtime reliability across nodes.
  • Removed obsolete internal replacements and cleaned up dependency mappings to simplify module resolution.

[coderabbitai]

📝 Walkthrough

Walkthrough

Bumps Thornode from v3.12.0 to v3.15.2 across Thorchain modules and updates related indirect dependencies (wasmd, wasmvm/v2) plus cometbft replace directives; removes an indirect cosmos/iavl replacement entry.

Changes

Cohort / File(s)	Summary
Thorchain coinstack module go/coinstacks/thorchain/go.mod	Require upgraded: gitlab.com/thorchain/thornode/v3 v3.12.0 → v3.15.2; indirect bumps: github.com/CosmWasm/wasmd v0.53.0 → v0.54.0, github.com/CosmWasm/wasmvm/v2 v2.1.2 → v2.2.1; updated replace for cometbft/cometbft v0.38.19 → v0.38.21; removal of an indirect cosmos/iavl replace.
Thorchain package module go/pkg/thorchain/go.mod	Same Thornode and CosmWasm indirect bumps; cometbft/cometbft require changed (noted to v0.39.0-beta.2 in this file); updated replace mapping to v0.38.21. No public API changes.
Thorchain v1 coinstack module go/coinstacks/thorchain-v1/go.mod	Require upgraded: gitlab.com/thorchain/thornode/v3 v3.12.0 → v3.15.2; indirect bumps for wasmd and wasmvm/v2 to same newer versions.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• chore: upgrade thorchain v3.12.0 #1199: Updates overlapping Thornode/cometbft dependency pins in Thorchain go.mod files.
• chore: upgrade cosmos to v25.3.2 #1259: Overlaps with cometbft replace and CosmWasm wasmvm/version bumps present here.

Poem

🐇 I hopped through go.mod fields today,
Thornode climbed a few rungs up the way,
WASM and Comet took a spin,
Replacements trimmed, versions in,
A carrot-tuned build — hip hooray! 🥕

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: upgrading thorchain to v3.15.2 across multiple go.mod files, which is the primary objective of the pull request.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Merge Conflict Detection	✅ Passed	✅ No merge conflicts detected when merging into develop

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch thorchain-v3.15.2

---

No actionable comments were generated in the recent review. 🎉

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@go/pkg/thorchain/go.mod`:
- Line 15: Update the wasm VM dependency to address critical vulnerabilities:
change the wasmvm module requirement to wasmvm/v2 v2.2.2 in go.mod (the
dependency is referenced as wasmvm/v2), run go mod tidy to refresh the lock, and
ensure you build/test (e.g., `go test ./...`) to catch any compile-time issues;
additionally, verify compatibility between wasmd v0.54.0 and the project’s
Cosmos SDK version (and coordinate a chain upgrade if moving to wasmd v0.54.0
since it pins wasmvm v2.2.x) before merging.