RUM-7337: Adjust Webview Replay storage configuration limits

[jonathanmos]

What does this PR do?

WebviewReplayFeature was using the default storage configuration. As a result, events sent by the browser sdk that were larger than 512kb were being rejected rather than written to batch files. This pr adjusts the size limits to align with session replay - 10mb per item and 10mb per batch.

I also added unit tests for WebviewReplayFeature as there didn't seem to be any.

Motivation

Support ticket where the customer couldn't see their webviews.

Additional Notes

Anything else we should know when reviewing?

Review checklist (to be filled by reviewers)

• Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
• Make sure you discussed the feature or bugfix with the maintaining team in an Issue
• Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 69.83%. Comparing base (bd71625) to head (c5ef356).
Report is 2 commits behind head on develop.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #2400      +/-   ##
===========================================
- Coverage    70.01%   69.83%   -0.17%     
===========================================
  Files          763      763              
  Lines        28374    28367       -7     
  Branches      4763     4763              
===========================================
- Hits         19864    19810      -54     
- Misses        7222     7243      +21     
- Partials      1288     1314      +26     

Files with missing lines	Coverage Δ
...id/webview/internal/replay/WebViewReplayFeature.kt	100.00% <100.00%> (+18.75%)	⬆️

... and 29 files with indirect coverage changes

---- 🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests

[0xnm]

I'm curious what can generate item with 10 MB size