Add structured log for request timeout on creator list endpoint

[Chucks1093]

Summary
When a creator list request times out, the timeout is surfaced to the client but not logged with structured context. A warn-level log at the timeout point with the elapsed time and request ID helps distinguish slow queries from infrastructure issues.

Scope

• identify where request timeouts are handled for the creator list endpoint
• add a warn-level structured log when a timeout occurs
• include elapsed time, request ID, and the active query params in the log fields

Acceptance Criteria

• a creator list timeout emits a warn-level log with elapsed time and request ID
• active query params are included to help reproduce the slow request
• the client timeout response is unchanged

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

[dominiccreates]

@dominiccreates 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 i am confident i can resolve the issue, having worked on and resolved similar issues

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

[shadrach68]

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

Hello, I’m interested in contributing to it as part of my open-source learning journey. I would appreciate it if you could assign me.

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

[Opulencechuks]

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

I would like to work on this because i can implement it having worked on similar issues

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

[eleven-smg]

@eleven-smg 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
I can start working now

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

[khanavi272-spec]

@khanavi272-spec 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

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

[drips-wave]

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

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