Determine recording size based on active window

[markushi]

📜 Description

Instead of relying on the window metrics, we now determine the size based on the top level Window View, once determined the RecordingConfig is created and actual recording is started.

I couldn't re-use the onConfigurationChanged hook, as it removes all rootViews. But in case of Dialogs, the root views are stacked and as soon as the dialog is popped, no more root view would be available.

I tried to apply my changes with minimal impact to the existing structure, happy to restructure it in a better way too, I simply wasn't sure how hybrids consume the existing APIs.

💡 Motivation and Context

Fixes #3574
Fixes #4358

💚 How did you test it?

Manual testing, see e.g. https://sentry-sdks.sentry.io/replays/f278df82391b4b30a7b1cb8b99b15578/?project=5428559&query=&referrer=%2Freplays%2F&statsPeriod=10m&yAxis=count%28%29

📝 Checklist

• I added tests to verify the changes.
• No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled.
• I updated the docs if needed.
• I updated the wizard if needed.
• Review from the native team if needed.
• No breaking change or entry added to the changelog.
• No breaking change for hybrid SDKs or communicated to hybrid SDKs.

🔮 Next steps

[github-actions]

Performance metrics 🚀

	Plain	With Sentry	Diff
Startup time	450.72 ms	452.60 ms	1.88 ms
Size	1.58 MiB	2.08 MiB	511.10 KiB

Previous results on branch: markushi/fix/stretched-dialogs-sr

Startup times

Revision	Plain	With Sentry	Diff
48b60cb	398.46 ms	433.92 ms	35.46 ms
168b278	427.60 ms	465.36 ms	37.76 ms
52710fb	449.32 ms	467.98 ms	18.66 ms
dd2d3a5	454.46 ms	493.24 ms	38.78 ms

App size

Revision	Plain	With Sentry	Diff
48b60cb	1.58 MiB	2.08 MiB	507.51 KiB
168b278	1.58 MiB	2.08 MiB	507.51 KiB
52710fb	1.58 MiB	2.08 MiB	511.11 KiB
dd2d3a5	1.58 MiB	2.08 MiB	511.10 KiB

[romtsn]

Would need to update tests I guess, but looks good! We'll also have to update Flutter with this change cc @vaind