refactor(logging): route frontend console calls through the logger

TRACES: | DR-204

484 ungated `console.*` calls across 63 non-test frontend files shipped to
end users with no way to turn them off. Mechanical substitution, no control
flow, error handling or message semantics changed:

  console.log / console.debug -> log.debug
  console.info                -> log.info
  console.warn                -> log.warn
  console.error               -> log.error

Hand-written `"[Scope] …"` prefixes are dropped where the logger's scope
now carries them; scope names that already existed are preserved verbatim
(`[Auth]`, `[VideoPlayer]`, `[PiP]`, …) and inferred from the filename
where a file had none. `src/routes/player/[id]/+page.svelte` keeps its
`NextEpisode` and `AutoPlay` sub-scopes as separate loggers rather than
flattening them into the page scope.

`grep -rn 'console\.' src/` now matches nothing outside the tests and the
facade itself.

src/lib/services/playbackCapabilities.ts

@@ -13,6 +13,9 @@
  */
 
 import { commands } from "$lib/api/bindings";
+import { createLogger } from "$lib/utils/logger";
+
+const log = createLogger("capabilities");
 
 export interface PlaybackCapabilities {
   /** Audio renders through a webview `<audio>` element, not a native backend. */
@@ -52,7 +55,7 @@ export async function getPlaybackCapabilities(): Promise<PlaybackCapabilities> {
       };
       return cached;
     } catch (err) {
-      console.warn("[capabilities] player_get_capabilities failed:", err);
+      log.warn("player_get_capabilities failed:", err);
       // Do NOT cache the fallback — a later call should get the real answer.
       return FALLBACK;
     } finally {