fix(opencode-plugin): respect log level in provider.models() catalog path (#8982)

[tientien17]

Summary

Follow-up to #9316 (fix(opencode-plugin): respect log level for lifecycle output). That PR gated the startup/lifecycle paths (init banner, auto-sync enabled, config-shim diagnostics) behind the leveled logger — but the provider.models() catalog path and the fetchers feeding it still emitted raw console.warn, which bypasses features.logLevel entirely and spills into the TUI on every TTL cache refresh.

This PR threads the leveled logger through the provider path so features.logLevel gates it too (same pattern as #9316).

Changes

• createOmniRouteProviderHook — accepts logger in deps (falls back to createLogger(features.logLevel) when absent). All 8 raw console.warn sites converted:
  • no baseURL resolvable → logger.error (genuine misconfiguration; still visible at error level)
  • combos / enrichment / compression-metadata / /api/providers fetch fallbacks → logger.warn
  • catalog refreshed breadcrumb → logger.info (hidden at the default warn level — this was the per-TTL-refresh TUI spam)
  • combo-key collision + unresolved nested combo-refs → logger.warn
• OmniRoutePlugin factory — passes the instance logger into the provider hook (createOmniRouteProviderHook(resolved, { cache, logger })).
• defaultOmniRouteAutoCombosFetcher — optional 4th logger param (OmniRouteLoggerSink); its 3 warnings (404 / non-ok / network error) now go through the leveled sink. Threaded at all 3 call sites: provider hook, forceSyncOmniRouteModels, config hook.
• forceSyncOmniRouteModels — combos fetch-failed warning uses the existing leveled logger.
• buildStaticProviderEntry — optional logger param (same sink type); the 2 remaining static-path warnings (unresolvable nested refs, auto-combo key collision) now respect the level. Threaded from both config-hook call sites.
• New OmniRouteLoggerSink type ({ error?; warn; debug? }) — the minimal partial sink the config hook already injects; a full Logger satisfies it structurally.

Tests

Extended tests/log-level.test.ts (+4, matching #9316 conventions):

• logLevel: "error" suppresses the provider-path fallback warnings and the catalog-refresh breadcrumb
• logLevel: "debug" preserves the catalog-refresh breadcrumb
• no baseURL resolvable remains visible at error level (genuine errors are not silenced)
• default auto-combos fetcher 404 warning respects the threaded logger level

Full plugin suite: 338 pass / 0 fail (1 pre-existing skip). Build (ESM + DTS via tsup) clean.

Follow-ups (deliberately out of scope)

• One-time ReadableStream gemini sanitize warning (fetch-interceptor)
• debugLog* tool error messages (user-invoked debug utilities)

Fixes the remaining gap of #8982.