Trace Context in non-OTLP Log Formats uses snake case for field names currently: https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/compatibility/logging_trace_context.md

The OTLP/JSON which is another format where field names are recorded as text uses camelCase (traceId, spanId).

Should we change recommendation for non-OTLP formats to use use camelCase?

@open-telemetry/specs-logs-approvers @open-telemetry/specs-approvers what do you think?

Relation PR that previously suggested yet another approach (using dots to match ECS): #3469