Replace console.error with structured logging

[Copilot]

Consolidates error logging to use the existing logger utility with Bugsnag integration and Datadog tracing instead of raw console.error calls scattered throughout the codebase.

Changes

• Replaced 54 console.error instances with logger.error() across API routes, server components, client components, and utilities
• Added ESLint enforcement: no-console rule (allows only warn/info) with explicit disables for logging infrastructure (logger.ts, bugsnag.ts, Errors.tsx)
• Library code (libs/base-ui): Made console.error conditional on isDevelopment to avoid cross-package dependencies
• Improved error handling: farcaster API route now returns 500 immediately when API_KEY is missing instead of logging and continuing

Example

Before:

} catch (error) {
  console.error('Registration error:', error);
  return NextResponse.json({ error: 'Internal server error' }, { status: 500 });
}

After:

} catch (error) {
  logger.error('Registration error', error);
  return NextResponse.json({ error: 'Internal server error' }, { status: 500 });
}

The logger provides structured logging with trace context, reports to Bugsnag in production, and maintains consistent error formatting across the application.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[github-advanced-security]

Bearer found more than 20 potential problems in the proposed changes. Check the Files changed tab for more details.