[SR] Handle orientation change

[romtsn]

#skip-changelog

📜 Description

• Observe device configuration changes to stop and restart the replay with new config
  • This is only support in full session mode for now, to support this in buffer mode we'd have to split the buffered video into multiple segments (as many as the number of orientation changes), but this will come later
• Fix bug where we were not tagging events with replayId in session mode

💡 Motivation and Context

Part of getsentry/sentry#63255

[github-actions]

Performance metrics 🚀

	Plain	With Sentry	Diff
Startup time	357.50 ms	436.94 ms	79.44 ms
Size	1.70 MiB	2.30 MiB	618.42 KiB

Baseline results on branch: rz/feat/session-replay-redact-options

Startup times

Revision	Plain	With Sentry	Diff
03382fb	320.57 ms	374.67 ms	54.10 ms
ff9aecd	359.28 ms	450.31 ms	91.03 ms
891e156	346.82 ms	407.51 ms	60.69 ms

App size

Revision	Plain	With Sentry	Diff
03382fb	1.70 MiB	2.30 MiB	617.80 KiB
ff9aecd	1.70 MiB	2.30 MiB	617.80 KiB
891e156	1.70 MiB	2.30 MiB	617.80 KiB

[markushi]

I'm wondering if onConfigurationChanged could be triggered without the width/height actually changing? Would it make sense to guard this the following way ~ if (oldConfig == newConfig) { return }

[romtsn]

yeah it can be triggered in the following cases

we're mostly interested in the first two, but I guess it's fine to stop and restart the recording for the others as well, just to make sure we don't try to encode different configurations into the same video segment, wdyt? Otherwise, we'd probably have to check what actually changed in the configuration, and if it's not window/screen size, then we do nothing.

[markushi]

Yeah it makes sense to me to create a new segment, let's keep it simple and check later if too many config changes are causing an issue 👍 (e.g. keyboard show/hide, network provider changing, ...)

[romtsn]

sounds good! I guess we'd need some kind of internal tracking for that, but that's for later