Unify structured logging attribute configuration and capture by default

Is your feature request related to a problem? Please describe.

Logging bridges use separate experimental properties for event-local structured fields:

• Log4j map-message-attributes.included and map-message-attributes.excluded
• Logback key-value-pair-attributes.included and key-value-pair-attributes.excluded
• Logback logstash-marker-attributes.included and logstash-marker-attributes.excluded
• Logback logstash-structured-argument-attributes.included and logstash-structured-argument-attributes.excluded

These sources all become OpenTelemetry log attributes, but users must configure each source separately. Structured fields deliberately attached to a logging event are also dropped by default.

Describe the solution you'd like

Introduce common selectors for event-local structured logging fields:

• otel.instrumentation.common.logging.structured-attributes.included
• otel.instrumentation.common.logging.structured-attributes.excluded
• java.common.logging.structured_attributes.included
• java.common.logging.structured_attributes.excluded

Apply them to Log4j MapMessage entries, SLF4J key-value pairs, Logback Logstash markers, and Logback Logstash structured arguments.

Use the normal all-by-default selector semantics. An absent or empty selector keeps all structured fields, an omitted included list keeps everything not excluded, and an exclude-only selector keeps everything except the excluded fields. Configure excluded=* to capture nothing. Keep existing value conversion, attribute collision precedence, and special handling for otel.event.name.

Keep MDC and logger-context selectors separate and opt-in because they contain ambient context rather than fields deliberately attached to the event.

Use the 3.0 transition to replace the source-specific experimental properties.

Tip

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.}