Add structured log for cache eviction events on creator endpoints

[Chucks1093]

Summary
When cached creator responses are evicted, there is no log entry to indicate why or when the eviction occurred. A debug-level structured log at the eviction point helps operators understand cache churn and tune TTLs without a full metrics setup.

Scope

• identify where cache evictions are triggered for creator endpoint responses
• add a debug-level structured log when an eviction occurs
• include the cache key and eviction reason in the log fields

Acceptance Criteria

• a cache eviction emits a debug-level log with key and reason
• the log does not appear at info level in production
• normal cache hits and misses are not affected

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

[Windowlight]

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

I’m interested in this issue and believe my experience with contracts, backend systems, and frontend implementation makes me a good fit. Happy to provide updates as I work through it.

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

[Georgechisom]

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

Hi, let me resolve this issue robustly

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

[Code-haeler]

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

Hiii, Good Morning Ser, I love your product, and I would love to solve this issue and solve it accurately.

Thank you for granting my request.

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

[drips-wave]

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

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

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