Add loading timeout fallback message for creator list

[Chucks1093]

Summary
Add loading timeout fallback message for creator list

Scope

• show fallback message after prolonged creator-list loading\n- provide retry action in fallback state\n- keep existing skeleton state behavior

Acceptance Criteria

• scoped change is implemented with no unrelated file churn
• docs/tests are updated where applicable
• contributor can validate the outcome locally

Contributor coordination: if you pick this up, reach out in Telegram for updates or clarification: https://t.me/accesslayerorg

[Stephan-Thomas]

@Stephan-Thomas has applied to work on this issue as part of the Stellar Wave Program's 4th wave.

hi, i would like to work on this.

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

[drips-wave]

Congratulations, @Stephan-Thomas! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on April 29, 2026.

🧑‍💻 @Stephan-Thomas: 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 🌊

[drips-wave]

This issue has been marked as completed by a Drips Wave moderator for @Stephan-Thomas as part of the Stellar Wave Program's 4th Wave 🥳

Moderator's reason: [Auto-assessed] The contributor has implemented the requested features: a 10-second timeout fallback message and a retry mechanism, while maintaining the existing skeleton loading state. The PR has been open for 5 days without any maintainer objections, and the code changes are clean and directly address the issue requirements.

😎 @Stephan-Thomas: You earned 100 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

ℹ️ Note: This issue was marked complete via moderation. Points were issued even though the GitHub issue remains open.