Allow injecting different OSLog into the framework

Hey Gui,

- [ ] Developers should have the ability to disable the os_log in production builds to protect user data.
- [ ] Developers should have the ability to customize the subsystem to their own need

Both can be achieved by providing a logging factory mechanism that can be overridden.

These can both be achieved by creating a factory or configuration passed into the transceiver at construction time. What are your thoughts on this as a privacy enhancement?

First thing I do when logging is make an extension on OSLog or Logger types that just take a category, the subsystem is usually the main bundle identifier.

Start by reviewing the transceiver construction API and the framework's existing OSLog usage. Determine how an overridable logging factory or configuration can disable production logging and customize the subsystem, then verify both privacy behaviors and custom subsystem support.

Do mô hình lập chỉ mục viết ra từ nội dung của issue.