Refactor error logging across the application to use a centralized logger

- Introduced a new logger utility (`logError`) to standardize error logging.
- Replaced all instances of `console.error` with `logError` in various API routes and libraries.
- Enhanced error logging to sanitize sensitive information, particularly for Prisma and Stripe errors.
- Ensured consistent error handling and logging practices throughout the codebase.

app/api/upload/audio/[filename]/route.ts

@@ -1,5 +1,6 @@
 import { apiErrors } from '@/lib/api-response';
 import { proxyR2MediaObject } from '@/lib/r2-media-proxy';
+import { logError } from '@/lib/logger';
 
 // Only allow UUID filenames with safe extensions
 const SAFE_FILENAME = /^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}\.[a-z0-9]+$/i;
@@ -39,7 +40,7 @@ export async function GET(
       internalErrorMessage: 'Failed to retrieve audio',
     });
   } catch (error: unknown) {
-    console.error('Error serving audio:', error);
+    logError('Error serving audio:', error);
     return apiErrors.internalError('Failed to retrieve audio');
   }
 }