High] inconsistent soroban sdk

[gloskull]

Motivation

• The repository contained inconsistent soroban-sdk versions across contract crates and the browser playground which can cause compile/runtime incompatibilities and contributor confusion.
• The goal is to pick a single, up-to-date Soroban Rust SDK and apply it uniformly so examples, CI, and the in-browser Cargo manifest align.

Description

• Updated all contract Cargo.toml files (workspace and individual crates) to use soroban-sdk = "26.1.0" and updated dev-dependencies to soroban-sdk = { version = "26.1.0", features = ["testutils"] } where present.
• Changed the playground default Cargo manifest (DEFAULT_CARGO_TOML in frontend/src/app/playground/page.tsx) to use soroban-sdk = "26.1.0" so browser-generated manifests match the repository standard.
• Updated the backend dependency registry metadata in backend/src/services/dependency-update.service.ts to list soroban-sdk/soroban-auth 26.1.0 and adjusted release notes to reference Protocol 26.
• Documented the selected SDK in README.md and updated unit/test fixtures and assertions (backend and frontend) to expect 26.1.0, including a resilient test assertion for the UI confirmation text in DependencyUpdatePanel.

Testing

• Verified no remaining files reference older soroban-sdk versions via repository search (used rg to confirm no 20.x, 21.x or 22.x occurrences remained) which succeeded.
• Ran backend unit tests for the dependency updater with pnpm test -- dependency-update.service.test.ts and they passed.
• Ran frontend unit tests for the dependency updater with pnpm exec vitest run src/components/playground/__tests__/DependencyUpdatePanel.test.tsx src/hooks/__tests__/useDependencyUpdates.test.ts and they passed after updating fixtures and assertions.
• cargo check --workspace and prisma generate could not be completed in this environment due to network restrictions (crates.io / Prisma engine downloads returned HTTP 403), so Rust/Cargo verification and generation of Prisma client artifacts were blocked and could not be exercised here.

Closes #997

[vercel]

@gloskull is attempting to deploy a commit to the Ayomide Adeniran's projects Team on Vercel.

A member of the Team first needs to authorize it.

[drips-wave]

@gloskull Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

[gloskull]

Hello, done with this project.

Please if you have anymore projects of this sort, do assign more to me... PR will be submitted in under 10hours.