Add shared async button loading component

[Chucks1093]

Summary
Add shared async button loading component

Scope

• add reusable async button with pending and disabled states\n- replace duplicated button loading patterns\n- keep API small and composable

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

[emdevelopa]

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

Hii maintainer I will like to jump on this issue

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

[viktrified]

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

I would like to work on this.

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

[DTriple-p]

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

Can I work on this issue?

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

[drips-wave]

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

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

[xqcxx]

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

Hi, I’d like to work on this issue. I have experience building full-stack applications with Soroban, handling both smart contract logic and frontend integration, and I’m comfortable debugging and delivering clean, maintainable solutions. I focus on clear communication and incremental updates to ensure smooth collaboration. I can complete this task within 24–48 hours while maintaining code quality and proper testing. Looking forward to contributing!

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

[drips-wave]

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

🧑‍💻 @xqcxx: 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 completed by @xqcxx as part of the Stellar Wave Program's 4th Wave 🥳

😎 @xqcxx: You earned 200 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. You can also Leave a review to share your experience working on this issue.

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