Add retry action to failed-transaction toasts

[miraclesonly]

Summary

• No retry or cancel button on failed transactions #250 (fixed): error toasts had no way to retry a failed action — the user had to dismiss the toast and manually re-trigger the whole flow (reopen a modal, re-enter an amount, click Connect again). useToast's handleError now accepts an optional onRetry callback; when passed, the toast renders an inline Retry button that closes the toast and re-invokes the same operation. Wired into the two most common failure points:
  • ConnectWalletButton — wallet connect failures (wrong network, rejected prompt, timeout) now retry handleConnect() directly.
  • UnlockModal — unlock transaction failures (simulation/submission errors) now retry handleUnlock() with the same amount/pool already in the form.
  • useToast.ts was renamed to useToast.tsx since it now renders JSX for the retry button.
• Farm page pool cards don't show lock status for connected wallet #249 (already resolved, no code change): asked for farm pool cards to show whether the connected user has an active lock in that pool. This was already added in the prior "Unlock status" countdown box on FarmPoolRow (merged in Noindex legacy redirect, farm-list lock status, themed ErrorBoundary (#227, #234, #235) #247 as part of the App doesn't show time remaining on locked positions in farm list #234 fix). Verified it's present and left an explanatory comment on the issue.
• PlatformStats component not used on home page #251 (investigated, no code change): asked why PlatformStats looks unused/duplicated with the home page's stat cards. PlatformStats is in fact used, on /farm (src/app/farm/page.tsx). The home page has its own separate stat-card UI (different metric set, framer-motion animation, gradient accent) built on the same usePlatformStats() hook, so there's no duplicate network fetch — React Query dedupes by query key. Merging the two into one shared component is a real design decision, not a soft fix, and forcing it here risked a visual regression on the most-viewed page. Left a comment explaining the trade-off instead.
• No skeleton loading for contributors page #252 (not applicable, no code change): asked for a loading skeleton on /contributors while data loads. Contributor data is a static JSON import (@/data/contributors.json), not fetched at runtime, so there's no async loading phase to skeleton-ize. Left a comment explaining this.

Test plan

• npx tsc --noEmit — no new errors beyond the pre-existing baseline (next.config.ts bundle-analyzer typing, soroban.ts Account name errors, TvlChart.tsx/soroban.ts TxHistoryEntry mismatch)
• npx eslint on all touched files — clean
• npx vitest run src/components/ConnectWalletButton/ConnectWalletButton.test.tsx — passes

Closes #250
Closes #249
Closes #251
Closes #252

[drips-wave]

@miraclesonly 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

[netlify]

❌ Deploy Preview for spiffy-melomakarona-eb1e8a failed.

Name	Link
🔨 Latest commit	d471545
🔍 Latest deploy log	https://app.netlify.com/projects/spiffy-melomakarona-eb1e8a/deploys/6a8e06cc7c7a690008daaf03

[netlify]

❌ Deploy Preview for smart-drop failed.

Name	Link
🔨 Latest commit	d471545
🔍 Latest deploy log	https://app.netlify.com/projects/smart-drop/deploys/6a8e06cca7c6940008a4c585