Library plants Timber.DebugTree() globally, affecting host app logging

[codeerow]

Hi!

LiveKit currently plants Timber.DebugTree() internally when loggingLevel != OFF
(if no DebugTree is present in the forest).

Since Timber is a global logger, this affects the entire host application,
not just LiveKit logs, and removes control over logging configuration
(e.g. custom Trees like Crashlytics-only logging).

Library code generally should not plant Timber trees, as this is an
application-level concern.

Suggested alternatives:

• Do not plant any Timber Tree, only log via Timber with a specific tag
• Provide a logger interface / callback so the host app decides where logs go
• Expose a flag or API to opt out of planting DebugTree

Thanks!