Fix Resource field type in Logs Data Model

[pellared]

Changes

Change the type of Resource to reference the definition in the SDK so that the resource's scheme URL is included in logs data model.

Why

The Logs Data Model misses scheme URL of resource. All of the languages reuse a common type representing resource.

• Java (stable logs): reuses a common resource type
• .NET (stable logs): reuses a common resource type
• C++ (stable logs): reuses a common resource type
• Python (experimental logs): reuses a common resource type

These changes can be seen as breaking. However, there is 100% precedence of how log attributes and resource are currently handled in all languages. I see the current description as a bug because we would miss scheme URL of the resource. AFAIK the intention of the OTel Logs Specification authors was to have only nested values for Body and Attributes.

Related PRs:

• Support maps and heterogeneous arrays as attribute values #2888
• log: Add design doc opentelemetry-go#4809

[tigrannajaryan]

This has been open for 2 days, has enough approvals, merging.