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/search/route.ts

@@ -3,6 +3,7 @@ import { db } from '@/lib/db';
 import { auth } from '@/lib/auth';
 import { apiErrors, successResponse } from '@/lib/api-response';
 import { checkRateLimit, rateLimitHeaders, RATE_LIMIT_CONFIGS } from '@/lib/rate-limit';
+import { logError } from '@/lib/logger';
 
 const MAX_Q_LENGTH = 100;
 const RESULTS_PER_CATEGORY = 5;
@@ -114,7 +115,7 @@ export async function GET(request: NextRequest) {
     response.headers.set('Cache-Control', 'private, no-store');
     return response;
   } catch (err) {
-    console.error('[search] error:', err);
+    logError('[search] error:', err);
     return apiErrors.internalError();
   }
 }