fix: disable pino-pretty in compiled Bun binaries

Adds isCompiledBinary() detection to identify when running in a compiled
Bun binary by checking if import.meta.url starts with file:///$bunfs/.

### Fixes
- Disable pino-pretty transport in compiled binaries to prevent runtime
  resolution errors since pino-pretty cannot be resolved from the virtual
  /$bunfs/ filesystem
- Add JSDoc comments explaining compiled binary detection logic

### Technical Details
- Compiled Bun binaries use a virtual /$bunfs/ filesystem where external
  modules like pino-pretty are not accessible at runtime
- isPrettyMode() now returns false for compiled binaries regardless of
  DEBUG or NODE_ENV settings

Author: llbbl

src/lib/logger.ts

@@ -1,10 +1,22 @@
 import pino from "pino";
 
+/**
+ * Detect if running in a compiled Bun binary.
+ * Compiled binaries run from /$bunfs/ virtual filesystem.
+ */
+function isCompiledBinary(): boolean {
+  return import.meta.url.startsWith("file:///$bunfs/");
+}
+
 /**
  * Determine if we should use pretty printing.
  * Pretty print when DEBUG is set or NODE_ENV=development.
+ * Never use pretty printing in compiled binaries (pino-pretty can't be resolved).
  */
 function isPrettyMode(): boolean {
+  if (isCompiledBinary()) {
+    return false;
+  }
   return Boolean(process.env.DEBUG) || process.env.NODE_ENV === "development";
 }