RUMM-2504: Switch to the SDK v2 storage component

[0xnm]

What does this PR do?

This change does a switch to the Storage implementation written earlier. While it is not used as it should be in the feature configuration per SDK v2 plan, this change helps to minimize the diff of the transition and makes a proof that new component works.

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

Merging #1051 (00b79be) into feature/sdkv2 (f913074) will increase coverage by 0.02%.
The diff coverage is 88.24%.

@@                Coverage Diff                @@
##           feature/sdkv2    #1051      +/-   ##
=================================================
+ Coverage          82.83%   82.84%   +0.02%     
=================================================
  Files                306      306              
  Lines              10080    10089       +9     
  Branches            1642     1645       +3     
=================================================
+ Hits                8349     8358       +9     
  Misses              1230     1230              
  Partials             501      501              

Impacted Files	Coverage Δ
...id/v2/core/internal/storage/ConsentAwareStorage.kt	96.77% <ø> (-0.03%)	⬇️
.../internal/rum/WebViewRumFilePersistenceStrategy.kt	62.96% <33.33%> (-1.04%)	⬇️
...rnal/persistence/file/batch/BatchFileDataWriter.kt	81.82% <85.71%> (-3.90%)	⬇️
...istence/file/batch/BatchFilePersistenceStrategy.kt	100.00% <100.00%> (ø)
...tadog/android/rum/internal/domain/RumDataWriter.kt	85.71% <100.00%> (+0.53%)	⬆️
.../rum/internal/domain/RumFilePersistenceStrategy.kt	100.00% <100.00%> (ø)
...n/kotlin/com/datadog/android/timber/DatadogTree.kt	50.00% <0.00%> (-5.56%)	⬇️
...g/internal/domain/event/DdSpanToSpanEventMapper.kt	95.92% <0.00%> (-4.08%)	⬇️
...tadog/android/tv/LeanbackViewAttributesProvider.kt	86.21% <0.00%> (-2.68%)	⬇️
...main/kotlin/com/datadog/android/rx/DatadogRxExt.kt	100.00% <0.00%> (ø)
... and 9 more

[mariusc83]

aren't we concerned that we will keep too much data in HEAP ?

[0xnm]

Good question. For now we need to store both event and serialized event mostly because of the RUM, but maybe later on with once RUM will start using write scope to perform writes we can change it.

What is your expectation for the memory pressure during SR? How often and how big are going to be events received? I guess concern is mostly because of the bitmaps?

I would propose to add TODO for now. WDYT?

[mariusc83]

Yes I am mostly thinking for Bitmaps here, let's benchmark this when we get there and see how it goes.