fix: upgrade cosmos sdk to 0.47.15

[lumtis]

Description

Closes #3322

Summary by CodeRabbit

• New Features

  • Added a telemetry endpoint /systemtime to the zetaclient.

• Bug Fixes

  • Upgraded Cosmos SDK to version 0.47.15.
  • Resolved issues with unsupported transaction versions for Solana.
  • Improved handling of inbound vote message validations and nonce updates.

• Tests

  • Updated testing strategies, including relocation of tests and addition of Solana E2E performance tests.

• Documentation

  • Updated changelog to reflect version v24.0.0 and recent changes.

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request primarily focuses on upgrading the Cosmos SDK to version 0.47.15 and updating the changelog for version v24.0.0. The changes encompass modifications to the go.mod file, updating the Go version and Cosmos SDK dependency, and expanding the changelog to document new features, tests, refactors, and fixes across the project.

Changes

File	Change Summary
changelog.md	Added v24.0.0 version entry with updates to features, tests, refactors, and fixes
go.mod	Updated Cosmos SDK dependency from v0.47.14 to v0.47.15 and Go version from 1.22.7 to 1.22.8

Assessment against linked issues

Objective	Addressed	Explanation
Upgrade Cosmos SDK to 0.47.15 [#3322]	✅

Possibly related PRs

• chore: fix changelog for v21 #3052: Changelog update for v21.0.0
• docs: changelog for v23 #3190: Changelog update for v23.0.0

Suggested reviewers

• fbac
• skosito
• kingpinXD
• brewmaster012
• swift1337
• ws4charlie

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

changelog.md (1)

33-35: Consider adding more details about the SDK upgrade.

While the entry correctly documents the upgrade, it would be helpful to include:

• The reason for the upgrade (e.g., security fixes, performance improvements)
• Any breaking changes or migration steps required
• Impact on existing functionality

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between faf1f79 and 6fcc4d6.

⛔ Files ignored due to path filters (1)

• go.sum is excluded by !**/*.sum

📒 Files selected for processing (2)

• changelog.md (1 hunks)
• go.mod (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• go.mod

🔇 Additional comments (1)

changelog.md (1)

Line range hint 1-24: LGTM! Well-structured changelog organization.

The changelog follows best practices with:

• Reverse chronological order
• Clear categorization (Features, Tests, Refactor, Fixes)
• PR links for traceability
• Unreleased section for pending changes