Update Logging API/SDK end use documentation

Is your feature request related to a problem?

As part of Logging API/SDK becoming stable, it would help to update the documentation around end use and expectations. Concerns in Sept 2025 with current state were:

2. only the root logger is instrumented, so seen loggers must have propagate set to True
3. the root logger is instrumented, so handlers on it must not be cleared and if you are loading logging settings with logging/.config.dictConfig, you must save the root loggers before applying dictConfig, then re-apply missing handlers

Describe the solution you'd like

Update the Logging API/SDK documentation, for example at the readthedocs and at otel.io auto-instrumentation example:

• https://opentelemetry-python.readthedocs.io/en/stable/examples/logs/README.html
• https://opentelemetry.io/docs/zero-code/python/logs-example/

Describe alternatives you've considered

No response

Additional Context

CNCF Slack thread: https://cloud-native.slack.com/archives/C01PD4HUVBL/p1757081385395979

Would you like to implement a fix?

None

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.}

Start with the linked readthedocs logs example and the OpenTelemetry auto-instrumentation logs example. Review the documented expectations for root logger instrumentation, propagation, handlers, and dictConfig, then update both documentation locations so the stable Logging API/SDK behavior and configuration steps are accurate and consistent.