RUMM-2347: Provide core SDK context

[0xnm]

What does this PR do?

This change brings a complete DatadogContext which includes some core SDK information, like service name, env, time information, device information, etc.

Having DatadogContext allows to replace userInfoProvider, timeProvider, networkInfoProvider, deviceInfoProvider with it (currently replacement is done mostly in RUM, not everywhere).

The data inside DatadogContext is from the time the context was requested, there are no computed properties.

NB: this change doesn't bring any thread-safety invariants or non-blocking API, those will be addresses later.

Reference in iOS repository DataDog/dd-sdk-ios#916.

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 #988 (da2dd64) into feature/sdkv2 (7e3b57e) will increase coverage by 0.12%.
The diff coverage is 91.55%.

@@                Coverage Diff                @@
##           feature/sdkv2     #988      +/-   ##
=================================================
+ Coverage          82.79%   82.91%   +0.12%     
=================================================
  Files                295      295              
  Lines               9714     9823     +109     
  Branches            1590     1600      +10     
=================================================
+ Hits                8042     8144     +102     
- Misses              1190     1195       +5     
- Partials             482      484       +2     

Impacted Files	Coverage Δ
...src/main/kotlin/com/datadog/android/DatadogSite.kt	100.00% <ø> (ø)
.../android/core/internal/data/upload/UploadWorker.kt	83.33% <0.00%> (ø)
...core/internal/system/DefaultAndroidInfoProvider.kt	84.44% <ø> (ø)
...id/core/internal/system/NoOpAndroidInfoProvider.kt	100.00% <ø> (ø)
...n/com/datadog/android/v2/api/context/DeviceType.kt	100.00% <ø> (ø)
.../main/kotlin/com/datadog/android/rum/RumMonitor.kt	77.08% <66.67%> (-0.92%)	⬇️
...android/v2/core/internal/DatadogContextProvider.kt	81.03% <81.03%> (ø)
.../android/rum/internal/domain/scope/RumViewScope.kt	96.88% <87.32%> (-0.04%)	⬇️
...ndroid/rum/internal/domain/scope/RumActionScope.kt	98.44% <94.12%> (-0.01%)	⬇️
...roid/rum/internal/domain/scope/RumResourceScope.kt	97.91% <94.29%> (-0.01%)	⬇️
... and 23 more

[mariusc83]

isn't it public by default ?

[0xnm]

indeed, public can be removed here

[mariusc83]

You mean like an async call ? Maybe we can provide both ?

[0xnm]

We are currently not sure if we will expose core context provider as a part of public API. For internal needs we are ok with blocking call for now, considering the way we get context fields and what fields are added to the context, so keeping things simple for now.

[mariusc83]

why doing the conversion and not have one single NetworkInfo for both v1 and v2 ?

[0xnm]

good point. The thing is that we indeed have some duplication for models between V1 and V2: UserInfo as well, for example. Eventually it will be only one, duplication is only for the V1 to V2 transition period, to have smaller changes footprint in PRs.