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/components/library/ClearHistoryButton.svelte

@@ -11,6 +11,9 @@
 <script lang="ts">
   import { auth } from "$lib/stores/auth";
   import { isServerReachable } from "$lib/stores/connectivity";
+  import { createLogger } from "$lib/utils/logger";
+
+  const log = createLogger("ClearHistoryButton");
 
   interface Props {
     /** Series or season id to clear. */
@@ -51,7 +54,7 @@
       await auth.getRepository().clearWatchHistory(itemId);
       onCleared?.();
     } catch (e) {
-      console.error("Failed to clear watch history:", e);
+      log.error("Failed to clear watch history:", e);
       alert(
         `Could not clear watch history: ${e instanceof Error ? e.message : String(e)}`
       );