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

@@ -3,6 +3,7 @@ import { apiErrors, successResponse, withCacheControl } from '@/lib/api-response
 import { getBillingOverview } from '@/lib/billing';
 import { isStripeFeatureEnabled } from '@/lib/feature-flags';
 import { hasStripeRuntimeConfig, isStripeConfigured } from '@/lib/stripe';
+import { logError } from '@/lib/logger';
 
 export async function GET() {
   try {
@@ -39,7 +40,7 @@ export async function GET() {
 
     return withCacheControl(response, 'private, no-store');
   } catch (error) {
-    console.error('Error fetching billing overview:', error);
+    logError('Error fetching billing overview:', error);
     return apiErrors.internalError('Failed to fetch billing overview');
   }
 }