Replace Record limit methods with DroppedAttributes

[MrAlias]

Resolve #5186

Similar to the trace SDK, de-duplicate the attributes before dropping.

Note, this does not include any truncation of string and string slice attributes. That is left for a follow-up PR.

Follow-up Tasks

• Truncate string and []string value types to configured limit #5217
• Validate map value types to not contain duplicate keys #5218

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 84.3%. Comparing base (1ff2e71) to head (9c3e01b).

Additional details and impacted files

@@          Coverage Diff          @@
##            main   #5190   +/-   ##
=====================================
  Coverage   84.3%   84.3%           
=====================================
  Files        258     258           
  Lines      16974   17042   +68     
=====================================
+ Hits       14313   14383   +70     
+ Misses      2362    2360    -2     
  Partials     299     299           

Files	Coverage Δ
exporters/stdout/stdoutlog/record.go	100.0% <100.0%> (ø)
sdk/log/record.go	100.0% <100.0%> (ø)

... and 1 file with indirect coverage changes

[pellared]

I just want to say that I support the API changes (addition of DroppedAttributes and removal of AttributeCountLimit and AttributeValueLengthLimit).

I had no time to review this PR yet.

[XSAM]

Do we need benchmarks for AddAttributes and SetAttributes in the following tasks?

[MrAlias]

Do we need benchmarks for AddAttributes and SetAttributes in the following tasks?

We do. That is left to #5054