Document AnyValue attribute limits

[lmolkova]

#4485 suggests using the following limits for complex attribute values:

Attribute value length limit SHOULD be applied to all leaf string nodes in
AnyValue which SHOULD be truncated to the configured limit.

Leaf nodes of an AnyValue attribute SHOULD count toward the attribute count limit.
If the limit is reached, the SDK MUST drop the entire AnyValue attribute;
partial exports are not allowed.

As well as potential ability on AnyValue to estimate its total size (which can be done at the construction time for performance reasons).

We can consider a separate set of attribute limits specifically for complex values, including a total size limit and ability to estimate AnyValue object size.

It's related to #4006 - a similar set of limits would be applicable to the log body with a caveat that log bodies may need a separate limit since log bodies are expected to be larger than attributes and backends tolerate large log bodies much better.

Regardless of the #4485 outcome, we need to define limits at least for the log attributes.

[lmolkova]

Referencing relevant comments from the OTEP #4485 review:

• OTEP: Extending attributes to support complex values #4485 (comment) - clarify what to do when value count is reached
• OTEP: Extending attributes to support complex values #4485 (comment) - byte array truncation suggestions
• OTEP: Extending attributes to support complex values #4485 (comment) - attribute key limits

[pellared]

Related issue (it is already in the description but having it as a "bullet" make it more visible):

• No limits for log record Body, SeverityText, and map/array count of AnyValue #4006

[pellared]

Here is a PoC of minimal required changes in regards of limits and new (complex) attribute types:

• [EndGoal] [DoNotMerge] Extend the set of attribute value types #4636