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/PersonDetailView.svelte

@@ -6,6 +6,9 @@
   import LibraryGrid from "./LibraryGrid.svelte";
   import CachedImage from "$lib/components/common/CachedImage.svelte";
   import { goto } from "$app/navigation";
+  import { createLogger } from "$lib/utils/logger";
+
+  const log = createLogger("PersonDetailView");
 
   interface Props {
     person: MediaItem;
@@ -34,7 +37,7 @@
       movies = result.items.filter(item => item.kind === "movie");
       series = result.items.filter(item => item.kind === "series");
     } catch (e) {
-      console.error("Failed to load filmography:", e);
+      log.error("Failed to load filmography:", e);
     } finally {
       loading = false;
     }