Allow configuration of inner SDK `Logger` using `LoggingHandler`

Is your feature request related to a problem?

Currently, our recommended approach for collecting logs using the sdk is through the LoggingHandler, which encapsulates a LoggerProvider and instantiates a OT SDK Logger by calling get_logger internally. This is synonomous to tracing's get_tracer and metrics get_meter, which accept name, version and schema url to construct an InstrumentationScope. The different with metrics and tracing is that the recommended approach is to construct Tracer and Meter manually by using those apis instead of through a handler. So with our current recommendation, users who use LoggingHandler to instantiate an sdk Logger by default will always get __name__ as the instrumentation module name (which is hardcoded to the name of the file), blank library version and blank schema url. We should probably provide a way for users to populate InstrumentationScope values through the use of LoggingHandler.

Describe the solution you'd like

Most likely have to add a parameter to allow for configuration of the inner sdk Logger in LoggingHandler.

Describe alternatives you've considered

No response

Additional Context

No response

Would you like to implement a fix?

None

Start with docs/examples/logs/example.py and the LoggingHandler implementation, then inspect opentelemetry-sdk/src/opentelemetry/sdk/_logs/_internal/init.py around Logger and get_logger. Determine how LoggingHandler should expose instrumentation scope values, and add coverage showing that configured name, version, and schema URL reach the inner SDK Logger.