Enhance LogRecord Deserialization with Default Values for Missing Fields

[lalitb]

Changes

Creating separate PRs for the small issues I am finding while doing integration tests for logs.

As of now, deserialization of LogRecords fails if certain fields are missing in the JSON input. By introducing default values for these fields, we ensure the deserialization process handles missing fields gracefully, similar to the current behavior of the traces deserialization.

Please provide a brief description of the changes here.

Merge requirement checklist

• CONTRIBUTING guidelines followed
• Unit tests added/updated (if applicable)
• Appropriate CHANGELOG.md files updated for non-trivial, user-facing changes
• Changes in public API reviewed (if applicable)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 71.6%. Comparing base (5b238eb) to head (774637f).

Additional details and impacted files

@@           Coverage Diff           @@
##            main   #1773     +/-   ##
=======================================
- Coverage   71.6%   71.6%   -0.1%     
=======================================
  Files        136     136             
  Lines      20857   20857             
=======================================
- Hits       14953   14951      -2     
- Misses      5904    5906      +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.