Namespace collision between Session Replays and FileBlobs prevents S3 Lifecycle Management

Namespace collision between Session Replays and FileBlobs prevents S3 Lifecycle Management: There is a path collision in the underlying storage (S3) between Session Replay segments and generic FileBlobs.
• Replays use a retention-based prefix: "{retention_days or 30}/{project_id}/{replay_id}/{segment_id}" (e.g., 90/123/...):
• FileBlobs use a hashed path: shards/path (e.g., 90/7b0d/... where 90 is a hash prefix):