Logs: the package's native log filter replaces an app-set one; console objects log as [object Object]; console.trace not captured; Android captureLogsLevel scope #145

Found while documenting the 7.x beta (docs PR bugsee/docs#110). Checked against the source on main at 7.0.0-beta3; file:line references are to the SDK repo unless a repo is named. Not reproduced on a device unless a line says so.

• The package always installs its own native log filter (it drops duplicate console lines) and reinstalls it at launch/relaunch and when the module is created (BugseeModule.mm:952,1288, BugseeModule.java:150,246), so a native log filter the app sets itself is silently replaced.
• Console objects are logged as [object Object], not JSON; console.trace is not captured.
• On Android captureLogsLevel applies only to lines read from logcat (BugseeCaptureDataProviderLog.onEvent), not to console.* lines forwarded through the wrapper channel nor to Bugsee.log; on iOS the level applies to every line.
• iOS com.bugsee.option.capture.logs.oslog is "PERMANENTLY DISABLED, accepted and ignored" in beta7 (BugseeOptions.h) but is still listed in src/options/option-keys.json.

Suggested direction

Chain the app's native filter instead of replacing it (this is what the wrapper-filters spec, bugsee/specs#58, is for), serialize objects, and apply one level semantics on both platforms.