update Cargo.toml for release v2.5.10

[nikhilsinhaparseable]

Summary by CodeRabbit

• Chores
  • Bumped version to 2.5.10 with updated UI assets and integrity checksums.

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

[coderabbitai]

Walkthrough

Bumps package version from 2.5.9 to 2.5.10 in Cargo.toml and updates the associated build assets URL and SHA1 hash to reference the new version.

Changes

Cohort / File(s)	Summary
Version and Asset Metadata Update Cargo.toml	Incremented package version to 2.5.10, updated parseable_ui assets URL to reference v2.5.10 build, and updated corresponding SHA1 hash for asset integrity verification

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• update Cargo.toml for release v2.5.9 #1524: Previous version bump from 2.5.8 to 2.5.9 with identical pattern of updating Cargo.toml metadata fields
• update Cargo toml for release v2.5.1 #1463: Version bump with same Cargo.toml fields updated (package.version and parseable_ui assets-url/sha1)
• chore: update Cargo.toml for release v2.5.7 #1515: Similar version release with matching Cargo.toml metadata updates for assets

Suggested reviewers

• nitisht

Poem

🐰 A tiny hop, a version new,
From 2.5.9 to 2.5.10 we flew,
Assets bundled, checksums align,
Build assets v2.5.10—simply divine! 📦✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The pull request has no description provided. The repository requires a description following a specific template with sections for Fixes, Description, and testing/documentation checkboxes.	Add a pull request description following the repository template, including issue reference, description of changes, and completion of required checkboxes.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely summarizes the main change: updating Cargo.toml for the v2.5.10 release, which is exactly what the changeset does.
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.}

---

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