RUM-5814 Provide device and os info into local spans metadata

[mariusc83]

What does this PR do?

After a short analysis on our local traces vs the traces created by RUM backend based on our RUM resource events we realized that we are missing some content for the local ones: device and os informations.
In this PR we are aligning the information in the local traces vs RUM backend traces by adding the device and os information into the local traces meta.

Please note that in order to keep schemas aligned I added these new properties also into the benchmark module span-schema.json but made them optional as right now the benchmark module is not using these (we might need it later).

Motivation

What inspired you to submit this pull request?

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

Attention: Patch coverage is 97.91667% with 1 line in your changes missing coverage. Please review.

Project coverage is 70.40%. Comparing base (fcfbbab) to head (f6ef7b5).
Report is 2 commits behind head on develop.

Files with missing lines	Patch %	Lines
...al/domain/event/CoreTracerSpanToSpanEventMapper.kt	83.33%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #2347      +/-   ##
===========================================
+ Coverage    70.33%   70.40%   +0.06%     
===========================================
  Files          740      741       +1     
  Lines        27633    27643      +10     
  Branches      4628     4624       -4     
===========================================
+ Hits         19435    19460      +25     
+ Misses        6909     6901       -8     
+ Partials      1289     1282       -7     

Files with missing lines	Coverage Δ
...trace/internal/domain/event/BaseSpanEventMapper.kt	100.00% <100.00%> (ø)
...e/internal/domain/event/DdSpanToSpanEventMapper.kt	93.62% <100.00%> (+5.09%)	⬆️
...al/domain/event/CoreTracerSpanToSpanEventMapper.kt	93.02% <83.33%> (+1.27%)	⬆️

... and 25 files with indirect coverage changes

[xgouchet]

Note

Maybe we could make this a BaseSpanEventMapper<T>: ContextAwareMapper<T, SpanEvent>, as it's only used on classes that extend this, and the purpose of this class is linked with creating SpanEvent content.