feat(backend): wire up shared Redis caching layer using cache-manager

[warisu]

Description

This PR addresses issue #878 by integrating a global caching layer via cache-manager and Redis. This prevents redundant, heavy querying patterns against core collections (such as report summaries and static lists) by resolving items directly from memory stores.

Changes Introduced

• Resilient Global Infrastructure Configuration: Embedded async setup loops ensuring connection drops yield warning traces rather than service termination.
• Typed Access Controls: Created custom service hooks handling data mutations cleanly.
• State Invalidation Paths: Hooked drop logic across target post/put modification methods to keep local cache states clean.

Acceptance Criteria Verified

• Active retrieval hits store outputs in memory layers successfully.
• Running write statements clears existing cache references cleanly.
• Dropping active Redis container connections switches execution logic to graceful fallback states smoothly.

Closes #878

[vercel]

@warisu is attempting to deploy a commit to the naijabuz's projects Team on Vercel.

A member of the Team first needs to authorize it.

[drips-wave]

@warisu Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits