fix(vesting): add admin auth guard and aggregate getter functions (#359, #360)

[Amas-01]

Summary

Closes #359
Closes #360

Fixes two security/usability defects in the soropad vesting contract:

• Vesting: initialize has no require_auth #359 — Add admin.require_auth() guard to the initialize() function (missing auth check)
• Vesting: no aggregate getters, so index: None silently touches only the newest schedule #360 — Implement aggregate getter functions and release_all to eliminate N+1 pattern

Changes

Contract (contracts/vesting/src/lib.rs)

• Added admin.require_auth() as the first executable statement in initialize() before any storage access
• Added 5 new contract functions:
  • total_vested(recipient) — sums total vested across all schedules
  • total_released(recipient) — sums total released across all schedules
  • total_releasable(recipient) — sums currently releasable across all schedules
  • get_all_schedules(recipient) — returns Vec<Schedule> in a single contract call
  • release_all(recipient) — releases all unlocked tokens across all schedules in one auth+batched-transfer
• release_all uses recipient.require_auth() and single token_client.transfer() call
• All 44 tests pass (4 new + 40 existing), test snapshots updated

Frontend

• lib/vesting.ts — Added fetchAllVestingSchedules (public export) and buildReleaseAllTx
• lib/stellar.ts — Added fetchAllVestingSchedules (public export)
• hooks/useSoroban.ts — Added fetchAllVestingSchedules callback and export
• ClaimVesting.tsx — Replaced N+1 pattern (fetchScheduleCount + loop) with single get_all_schedules call;
  added "Release All" button when multiple schedules exist
• PersonalDashboard.tsx — Same N+1 fix using fetchAllVestingSchedules; kept fetchVestingScheduleCount for
  backward compat

Testing

• cargo test — 44/44 pass
• cargo fmt --all -- --check — clean (vesting contract)
• tsc --noEmit — passes
• next lint — no new warnings

[drips-wave]

@Amas-01 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

[zachyo]

Hi @Amas-01 , kindly fix conflicts, clear out test json and fix lib