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

@@ -5,6 +5,7 @@ import { acceptInvitationTokenForUser, getValidInvitationByToken } from '@/lib/i
 import { checkRateLimit, getClientIp, rateLimitHeaders, RATE_LIMIT_CONFIGS } from '@/lib/rate-limit';
 import { apiErrors, successResponse, withCacheControl } from '@/lib/api-response';
 import { isInviteCodeRequired } from '@/lib/feature-flags';
+import { logError } from '@/lib/logger';
 
 export async function POST(request: NextRequest) {
     try {
@@ -128,7 +129,7 @@ export async function POST(request: NextRequest) {
 
         return withCacheControl(response, 'private, no-store');
     } catch (error) {
-        console.error('Registration error:', error);
+        logError('Registration error:', error);
         return apiErrors.internalError('Failed to create account');
     }
 }