RUMM-2536: Use SDK v2 configuration interfaces for features

[0xnm]

What does this PR do?

This change does the following decouples SdkFeature from RUM, Logs, etc. features. SdkFeature will reside in the core module and won't be exposed as part of the public API, it is responsible for Storage and Uploader creation. RUM, Logs, etc. features will be in the independent modules.

For now they take Storage as a constructor argument, but later on they will only depend on SdkCore and will do the writing operations using Event Write Context via SdkCore#getFeature -> FeatureScope#withWriteContext call. SdkFeature implements FeatureScope.

The idea is that RumFeature, LogsFeature, etc. will be handling data serialization (since it is not the responsibility of the core) and will write the binary data in the EWC, so for their own PersistenceStrategy interface we are leaving DataWriter part only.

DatadogFeature class is removed in favour of SdkFeature.

Features lifecycle API will be decided later.

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 #1079 (3b40dae) into feature/sdkv2 (3200133) will decrease coverage by 0.01%.
The diff coverage is 81.77%.

@@                Coverage Diff                @@
##           feature/sdkv2    #1079      +/-   ##
=================================================
- Coverage          82.57%   82.56%   -0.01%     
=================================================
  Files                347      346       -1     
  Lines              11202    11157      -45     
  Branches            1845     1831      -14     
=================================================
- Hits                9249     9211      -38     
- Misses              1378     1383       +5     
+ Partials             575      563      -12     

Impacted Files	Coverage Δ
...oid/src/main/kotlin/com/datadog/android/Datadog.kt	71.43% <0.00%> (-1.12%)	⬇️
...istence/file/batch/BatchFilePersistenceStrategy.kt	100.00% <ø> (ø)
...ror/internal/CrashReportFilePersistenceStrategy.kt	100.00% <ø> (ø)
.../src/main/kotlin/com/datadog/android/log/Logger.kt	93.89% <ø> (ø)
.../log/internal/domain/LogFilePersistenceStrategy.kt	100.00% <ø> (ø)
...c/main/kotlin/com/datadog/android/rum/GlobalRum.kt	63.04% <0.00%> (-5.85%)	⬇️
...droid/rum/tracking/FragmentViewTrackingStrategy.kt	78.85% <0.00%> (ø)
...oid/rum/tracking/NavigationViewTrackingStrategy.kt	84.48% <0.00%> (-0.26%)	⬇️
...l/domain/SessionReplayRecordPersistenceStrategy.kt	100.00% <ø> (ø)
...g/internal/domain/TracesFilePersistenceStrategy.kt	100.00% <ø> (ø)
... and 28 more

[mariusc83]

for now we are still doing the writing through the persistenceStrategy?

[0xnm]

for now - yes. In the later PRs this will change: interface of DataWriter will change (and it won't be a single interface in the core) and for cross-feature interaction we will have message bus instead of getting the writer of another feature.