feat: tidy some context on replay events

[pauldambra]

we talked about adding context to our recording viewed and analyzed events so we can track useful things like "are people watching more from playlists"

these are backend events

we capture current URL on these but since they can contain different IDs breakdown by them is yucky

let's do some simple cleaning as we capture these events (since a hogql multistep regex replace is messy to maintain)

i got to here with regex in hogql

and i didn't want to maintain that

[greptile-apps]

PR Summary

This PR adds URL path cleaning functionality to standardize session recording event analytics, particularly for tracking recording views from different sources like playlists.

• Added clean_referer_url function in /posthog/session_recordings/session_recording_api.py to standardize URLs into categories like 'person-page', 'insight', 'replay-direct'
• Added comprehensive test suite in /posthog/session_recordings/test/test_clean_referer_url.py with parameterized test cases covering various URL patterns
• Added cleaned_replay_path to event properties in SessionRecordingViewSet.update() for better analytics breakdowns
• Implemented error handling with posthoganalytics.capture_exception for URL cleaning failures

_{3 file(s) reviewed, 1 comment(s)
Edit PR Review Bot Settings | Greptile}

[github-actions]

Size Change: +5 B (0%)

Total Size: 1.17 MB

ℹ️ View Unchanged

Filename	Size	Change
frontend/dist/toolbar.js	1.17 MB	+5 B (0%)

_{compressed-size-action}

[veryayskiy]

And I have an addition to you for that - see last two pictures here: #28211