[S4] Add typed API response interfaces for Pool, Donation, and User

[Akshola00]

Description

Define TypeScript interfaces that match the API response shapes from the NestJS server so all API calls are type-safe.

Deliverables

• Create lib/api-types.ts (or add to existing types file)
• ApiPool: id, contractPoolId, title, description, category, creatorWallet, status, goal, raised, imageUrl, raisedOnChain, donorCount, createdAt
• ApiDonation: id, txHash, poolId, poolTitle, donorWallet, amount, asset, createdAt
• ApiUser: id, publicKey, displayName, createdAt
• PaginatedResponse<T>: data, total, page, limit
• All existing API call functions updated to use these types
• npm run build passes with no type errors

Notes

Depends on #56–58. Keep interfaces separate from the Zustand store types — the store can have its own shape.

[GEEKYFOCUS]

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

Hello Team Nevo, the requirements for this feature are clear to me. My approach would be to implement it incrementally, validate edge cases, and ensure it integrates smoothly with existing functionality.

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

[Victorjonah-prog]

@Victorjonah-prog 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 because I specialize in TypeScript API typing. I can create clean interfaces (ApiPool, ApiDonation, ApiUser, PaginatedResponse) in lib/api-types.ts and update all API calls to use them while keeping them separate from store types.

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

[Zinai10]

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

Hi Maintainer! I would like to work on this issue

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

[drips-wave]

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

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