Investigate cache key expiration and TTL tuning for search_finders_redis_cache before FF rollout
Before releasing the `search_finders_redis_cache` feature flag introduced in !224795, investigate the following:
- [ ] Determine if event-based cache key expiration (e.g., on permission changes) is worthwhile. @michaelangeloio explored this previously — need to follow up on where that landed.
- [ ] Evaluate whether the 5-minute TTL should be tuned further.
## Context
!224795 adds a short-lived Redis cache (5-minute TTL) for `Search::GroupsFinder` and `Search::ProjectsFinder` behind the `search_finders_redis_cache` feature flag. The TTL is intentionally short to bound worst-case permission staleness (e.g., user removed from a project), but these open questions should be resolved before the FF is fully rolled out.
issue