Top opentelemetry-specification issues

Define what `required` means for a semantic convention

semantic-conventions p2 allowed-for-ga resource trace

Rename span.end() to span.finish()

Limitation on number of attributes, links, events and behavior

sdk needs discussion after-ga trace

ValueRecorder - default aggregation

api p1 required-for-ga metrics

Support map values and nested values for attributes

api semantic-conventions enhancement needs discussion after-ga

Event is one of the major verticals as well as Metrics, Tracing and Logging in observability from my perspective

api semantic-conventions needs discussion after-ga metrics trace

OpenTelemetry should use an allowed port

miscellaneous p1 required-for-ga protocol

Adding resource attributes post-creation (e.g. via auto-discovery)

data-model sdk after-ga protocol resource

Service name should be mandatory for all configured resources.

sdk p1 required-for-ga resource

Revert use of PropagatedSpan back to using a special Context key for extracted Span Context

api p1 required-for-ga trace