Add integration test for creator list response shape consistency across page sizes

[aniokedianne]

Summary
Creator list responses with page size of one, ten, and the maximum should all return the same top-level response shape. An integration test across multiple page sizes confirms the envelope structure is consistent regardless of result count.

Scope

• add an integration test that requests the creator list at three different page sizes
• assert the top-level response shape is identical across all three responses
• assert only the items array length and pagination metadata differ between responses

Acceptance Criteria

• the response envelope shape is identical for all tested page sizes
• the items array length matches the requested page size or the total available
• the test uses a fixture with enough creators to produce varied result counts

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

[kimanicode]

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

I would like to work on this issue because consistent API response shapes prevent fragile frontend integrations and subtle bugs. I've written similar pagination integration tests before. I'll test creator list responses at page sizes 1, 10, and max, asserting the envelope shape stays identical while items length and pagination metadata vary appropriately.

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

[ritik4ever]

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

Hi
I’d like to work on this issue if it’s available. I’m a full-stack Web2 & Web3 developer with solid open-source experience and can start working on it right away.

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

[drips-wave]

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

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

😎 @ritik4ever: 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.