Is your feature request related to a problem? Please describe.
In legacy java application methods like log.info("Message {}, {} and {}, arg1,arg2,arg3) often happens in code.
It would be convenient to store such log arguments in telemetry for log search functionality without using full-text search.
Describe the solution you'd like
Save ILoggingEvent.getArgumentArray() into AttributesBuilder in the existing io.opentelemetry.instrumentation.logback.appender.v1_0.internal.LoggingEventMapper.mapLoggingEvent() and save log message pattern as attribute also.
Introduce capture-arguments boolean parameter to switch on/off this functionality as part of otel.instrumentation.logback-appender.experimental. and OpenTelemetryAppender

Describe alternatives you've considered
Use the structured log body for log arguments capture in OpenTelemetry for logback
Additional context
No response
Is your feature request related to a problem? Please describe.
In legacy java application methods like log.info("Message {}, {} and {}, arg1,arg2,arg3) often happens in code.
It would be convenient to store such log arguments in telemetry for log search functionality without using full-text search.
Describe the solution you'd like
Save ILoggingEvent.getArgumentArray() into AttributesBuilder in the existing io.opentelemetry.instrumentation.logback.appender.v1_0.internal.LoggingEventMapper.mapLoggingEvent() and save log message pattern as attribute also.
Introduce capture-arguments boolean parameter to switch on/off this functionality as part of otel.instrumentation.logback-appender.experimental. and OpenTelemetryAppender
Describe alternatives you've considered
Use the structured log body for log arguments capture in OpenTelemetry for logback
Additional context
No response