Add device.architecture to logs

[fuzzybinary]

What does this PR do?

This adds a device.architecture property to logs. Device is kept as an object for potential future expansion

Motivation

The device architecture is needed for Flutter symbolication of logs.

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 #1140 (2de7fa4) into develop (931b063) will increase coverage by 0.02%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##           develop    #1140      +/-   ##
===========================================
+ Coverage    83.17%   83.20%   +0.02%     
===========================================
  Files          274      274              
  Lines         9462     9470       +8     
  Branches      1540     1540              
===========================================
+ Hits          7870     7879       +9     
  Misses        1152     1152              
+ Partials       440      439       -1     

Impacted Files	Coverage Δ
...n/com/datadog/android/core/internal/CoreFeature.kt	91.74% <100.00%> (+0.03%)	⬆️
...adog/android/error/internal/CrashReportsFeature.kt	100.00% <100.00%> (ø)
.../src/main/kotlin/com/datadog/android/log/Logger.kt	96.06% <100.00%> (+0.03%)	⬆️
...atadog/android/log/internal/domain/LogGenerator.kt	99.07% <100.00%> (+0.05%)	⬆️
...android/log/internal/logger/TelemetryLogHandler.kt	75.00% <0.00%> (-25.00%)	⬇️
...rc/main/java/com/datadog/opentracing/DDTracer.java	55.65% <0.00%> (-0.42%)	⬇️
...ndroid/telemetry/internal/TelemetryEventHandler.kt	72.32% <0.00%> (ø)
...core/internal/system/DefaultAndroidInfoProvider.kt	82.61% <0.00%> (ø)
...android/rum/internal/ndk/DatadogNdkCrashHandler.kt	88.11% <0.00%> (+0.54%)	⬆️
.../android/rum/internal/monitor/DatadogRumMonitor.kt	93.33% <0.00%> (+0.56%)	⬆️
... and 1 more

[0xnm]

should we revert this change now?

[fuzzybinary]

Yes, good catch. I actually thought I did revert it.