Cache Logic

[madhavtibrewal]

Decide caching target (Event Service) | Decide which event data should be cached (event details, event list, RSVP lookups, etc.)
Introduce Redis in Event Service | Add Redis client, env config, DI wrapper, connection health check.
Cache GET /event/{id} | When an event is fetched by ID, store in cache; invalidate on update.

Maybe - > Cache list endpoint GET /events (Optional Sprint 2) | Cache popular query results to speed event discovery (can be added Sprint 3 if heavy).