update Cargo.toml for release v2.5.11

[nikhilsinhaparseable]

Summary by CodeRabbit

• Chores
  • Version bumped from 2.5.10 to 2.5.11
  • Package assets updated to latest build

[coderabbitai]

Walkthrough

Updated package version from 2.5.10 to 2.5.11 in Cargo.toml. Correspondingly updated the UI assets URL and SHA1 hash to reference the new version's build artifacts.

Changes

Cohort / File(s)	Summary
Version and Assets Update Cargo.toml	Bumped package version to 2.5.11 and updated parseable_ui assets-url and assets-sha1 to match the new release build.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• #1526: Updates Cargo.toml for consecutive releases (v2.5.10 → v2.5.11) with same fields modified.
• #1524: Makes identical changes to Cargo.toml—bumping package.version, assets-url, and assets-sha1.
• #1506: Updates the same Cargo.toml fields for package version and UI assets metadata.

Suggested reviewers

• nitisht

Poem

🐰 A version bump so clean and tight,
From 2.5.10 to 2.5.11's light!
Assets hash refreshed with care,
New builds ready everywhere!
Build the future, hop so far! 🚀

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The pull request description is empty, missing all required sections including description, rationale, key changes, and testing/documentation checklist items specified in the template.	Add a comprehensive description following the template, including: the purpose of the release update, key changes made (version bump and asset updates), and completion of the testing and documentation checklist.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically describes the main change: updating Cargo.toml configuration for the v2.5.11 release, which matches the version bumps and metadata updates in the changeset.
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.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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