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

@@ -6,6 +6,7 @@ import { rateLimit } from '@/lib/rate-limit';
 import { isStripeFeatureEnabled } from '@/lib/feature-flags';
 import { getStripe, isStripeConfigured } from '@/lib/stripe';
 import { isTrustedSameOriginRequest } from '@/lib/request-origin';
+import { logError } from '@/lib/logger';
 
 function getAppOrigin(request: NextRequest) {
   if (isTrustedSameOriginRequest(request)) {
@@ -54,7 +55,7 @@ export async function POST(request: NextRequest) {
     const response = successResponse({ url: portalSession.url });
     return withCacheControl(response, 'private, no-store');
   } catch (error) {
-    console.error('Error creating Stripe portal session:', error);
+    logError('Error creating Stripe portal session:', error);
     return apiErrors.internalError('Failed to open billing portal');
   }
 }