chore: update Cargo.toml for release v2.5.7

[nikhilsinhaparseable]

Summary by CodeRabbit

• Chores
  • Bumped version to 2.5.7 with updated package assets and checksums

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

This PR bumps the package version from 2.5.6 to 2.5.7 and updates the parseable_ui assets URL and SHA1 checksum in the Cargo.toml manifest to reference the corresponding v2.5.7 build artifacts.

Changes

Cohort / File(s)	Summary
Version & Metadata Update Cargo.toml	Bumped package version to 2.5.7; updated package.metadata.parseable_ui assets-url from v2.5.6/build.zip to v2.5.7/build.zip; updated assets-sha1 checksum

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• update Cargo toml for release v2.5.4 #1478: Version bump and parseable_ui assets metadata update in Cargo.toml
• chore: update Cargo.toml for release v2.5.5 #1506: Version bump and parseable_ui assets metadata update in Cargo.toml
• chore: update cargo toml for release-v2.3.4 #1358: Version bump and parseable_ui assets metadata update in Cargo.toml

Suggested reviewers

• nitisht

Poem

🐰 A version hops, from six to seven,
SHA1 checksums align with heaven,
Assets bundled, fresh and new,
Parseable shines in 2.5.2! 🚀

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	No pull request description was provided by the author, but the template requires sections for description, rationale, and checklist items.	Add a pull request description following the repository template, including the purpose of the release, key changes, and completion of the required checklist items.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly describes the main change: updating Cargo.toml for the v2.5.7 release, which matches the version bump in the summary.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

---

📜 Recent review details

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 31a3ad9 and 580e290.

⛔ Files ignored due to path filters (1)

• Cargo.lock is excluded by !**/*.lock

📒 Files selected for processing (1)

• Cargo.toml

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (9)

• GitHub Check: coverage
• GitHub Check: Build Default aarch64-apple-darwin
• GitHub Check: Build Default x86_64-unknown-linux-gnu
• GitHub Check: Build Default x86_64-pc-windows-msvc
• GitHub Check: Build Default aarch64-unknown-linux-gnu
• GitHub Check: Build Kafka x86_64-unknown-linux-gnu
• GitHub Check: Build Kafka aarch64-apple-darwin
• GitHub Check: Quest Smoke and Load Tests for Standalone deployments
• GitHub Check: Quest Smoke and Load Tests for Distributed deployments

🔇 Additional comments (2)

Cargo.toml (2)

3-3: LGTM! Version bump is correct.

The version has been correctly updated from 2.5.6 to 2.5.7 for the release.

---

184-185: Verify the SHA1 checksum matches the build artifact.

The assets URL correctly points to v2.5.7 and the artifact is accessible. However, the SHA1 checksum cannot be independently verified in the build environment. Ensure the checksum 16bcf0aa539e8e889c683b080bad94d5409a187d is validated against the actual build artifact before merging to confirm build integrity.

---

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