Filter noisy targets from persistent logs

[jif-oai]

Why

The local SQLite log sink currently enables TRACE for every target. This persists high-volume dependency logs bridged through target=log and duplicates OpenTelemetry mirror events in codex_otel.log_only and codex_otel.trace_safe.

These records rapidly consume the per-partition log budget and cause unnecessary SQLite insert-and-prune churn.

What changed

• Keep TRACE persistence for other targets.
• Exclude bridged target=log events from the SQLite sink.
• Exclude the two codex_otel mirror targets from the SQLite sink.
• Share the same filter between app-server and TUI.

Remote OpenTelemetry export and metrics are unchanged.