Add proper error states with retry functionality

[therealjhay]

Description: Currently, if data fails to load (e.g., API is down, network error), the app either shows mock data silently or shows a generic toast. Each data-dependent section should have a dedicated error state with a "Retry" button and a helpful message.

Requirements:

• Create an ErrorDisplay component with: error icon, message, and "Try Again" button
• Add error state handling to: dashboard stat cards, transactions table, payment links list, wallet balances, settlement history, FX rates
• Use React Query's isError state if applicable, or manual error state management
• The retry button should re-trigger the data fetch
• Show a subtle message, not a full-page takeover

Suggested execution steps:

1. Create components/shared/ErrorDisplay.tsx with message, onRetry props
2. In the wallet page, add error state: if refreshBalances fails, show ErrorDisplay in place of balances
3. In the transactions page, add error state: show ErrorDisplay in the table body
4. In the dashboard, add error boundary around each section
5. Use consistent amber/slate styling for the error display

Example commit message:

feat(ux): add error states with retry buttons to all data-dependent sections

Created ErrorDisplay component with icon, message, and "Try Again" button.
Added error handling to wallet balances, transactions table, payment links,
settlement history, and FX rates. Sections now gracefully degrade instead
of failing silently or showing stale mock data.

[Emoji-dot]

@Emoji-dot has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I would like to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Emoji-dot to this issue.

[Adiz4415]

@Adiz4415 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I would love to work on this issue, please assign the issues to me so i Can work on it ASAP

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Adiz4415 to this issue.

[fadesany]

@fadesany has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hello maintainer, i would like to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @fadesany to this issue.

[samjay8]

@samjay8 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hello Boss, I will like to work on this issue, please kindly assign this to me.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @samjay8 to this issue.

[abbys-code-hub]

@abbys-code-hub has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I would love to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @abbys-code-hub to this issue.

[drips-wave]

Congratulations, @fadesany! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @fadesany: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊