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/utils/safeArea.ts

@@ -36,6 +36,10 @@
  *    document exists, and a page load wipes any inline style native had set.
  */
 
+import { createLogger } from "$lib/utils/logger";
+
+const log = createLogger("SafeArea");
+
 /** Window insets in CSS pixels, one per edge. */
 export interface SafeAreaInsets {
   top: number;
@@ -135,7 +139,7 @@ export function readNativeInsets(): SafeAreaInsets | null {
   try {
     return parseNativeInsets(bridge.get());
   } catch (err) {
-    console.warn("[SafeArea] AndroidInsets bridge unusable:", err);
+    log.warn("AndroidInsets bridge unusable:", err);
     return null;
   }
 }