Simplify otel limits

[fractalwrench]

Goal

Simplifies the limits enforced on OTel data capture by rolling custom and system attributes + events into one. This should make it simpler for pure OTel folks to send as much data as they want by configuring the SDK appropriately.

Testing

Relied on existing test coverage.

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

OpenSSF Scorecard

Package	Version	Score	Details

Scanned Files

[codecov]

Codecov Report

Attention: Patch coverage is 94.52055% with 4 lines in your changes missing coverage. Please review.

Project coverage is 85.29%. Comparing base (f3c3d7f) to head (1d3cd32).
Report is 13 commits behind head on main.

Files with missing lines	Patch %	Lines
...droid/embracesdk/internal/spans/EmbraceSpanImpl.kt	93.33%	0 Missing and 2 partials ⚠️
...mbracesdk/internal/spans/CurrentSessionSpanImpl.kt	87.50%	0 Missing and 1 partial ⚠️
...droid/embracesdk/internal/spans/SpanServiceImpl.kt	83.33%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1746      +/-   ##
==========================================
- Coverage   85.31%   85.29%   -0.02%     
==========================================
  Files         464      464              
  Lines       10775    10754      -21     
  Branches     1591     1589       -2     
==========================================
- Hits         9193     9173      -20     
  Misses        870      870              
+ Partials      712      711       -1     

Files with missing lines	Coverage Δ
...ternal/capture/session/EmbraceSessionProperties.kt	96.49% <100.00%> (ø)
...nternal/config/instrumented/OtelLimitsConfigExt.kt	100.00% <100.00%> (ø)
...racesdk/internal/opentelemetry/OpenTelemetrySdk.kt	100.00% <100.00%> (ø)
...al/session/orchestrator/SessionOrchestratorImpl.kt	91.81% <100.00%> (ø)
...ssion/orchestrator/SessionSpanAttrPopulatorImpl.kt	93.93% <100.00%> (ø)
...oid/embracesdk/internal/spans/EmbraceExtensions.kt	78.12% <100.00%> (ø)
...mbracesdk/internal/spans/PersistableEmbraceSpan.kt	100.00% <ø> (ø)
...dk/internal/capture/activity/UiLoadTraceEmitter.kt	90.24% <100.00%> (ø)
...nal/config/instrumented/schema/OtelLimitsConfig.kt	100.00% <100.00%> (ø)
...mbracesdk/internal/spans/CurrentSessionSpanImpl.kt	88.75% <87.50%> (ø)
... and 2 more

[bidetofevil]

The reason we separated system and custom attributes is so we can have a lower limit for custom attributes (e.g. max 10 attributes per span) for customers that send us data.

With this new scheme how are we enforcing those lower limits?