RUM-10805: Remove resolveMeta & resolveMetrics methods in tests

[kikoveiga]

What does this PR do?

• Refactors trace integration tests to eliminate circular dependency to generate expected values.
• Improves the tests.

Motivation

resolveMeta and resolveMetrics methods used production code to generate expected values, then compared those values against the actual output.

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)

[datadog-datadog-prod-us1]

🎯 Code Coverage
• Patch Coverage: 94.78%
• Total Coverage: 71.33% (+0.00%)

View detailed report

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: d312ed9 | Docs | Datadog PR Page | Was this helpful? Give us feedback!}

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 71.22%. Comparing base (5cec742) to head (d312ed9).

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #3005      +/-   ##
===========================================
+ Coverage    71.17%   71.22%   +0.05%     
===========================================
  Files          859      859              
  Lines        31429    31429              
  Branches      5298     5298              
===========================================
+ Hits         22367    22384      +17     
+ Misses        7555     7550       -5     
+ Partials      1507     1495      -12     

Files with missing lines	Coverage Δ
...al/domain/event/CoreTracerSpanToSpanEventMapper.kt	90.22% <ø> (-2.17%)	⬇️

... and 32 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[0xnm]

I believe there should be something here?

[kikoveiga]

All the fields of SpanEvent.Usr are nullable and they are not used or set for these tests.

[0xnm]

Then this is something we shouldn't have. We should either set User object for the test or not add empty UserInfo object (like we do in RUM) to the trace event (or both), because sending object with empty property doesn't really make any sense.

Also I see that UserInfo.anonymousId is not set for the Span event, it is worth checking if it is on purpose or it is a miss.