FEAT: configure logger

[pedroanastacio]

Description

Some parts of the code base still rely on direct console.* calls (console.warn, console.error, console.log, etc.) to report errors and runtime information. While this works during development, it may not be ideal for production.
Replace direct console.* calls with the project's logger instance to ensure structured, consistent, and observable logs.

Summary

• Implements improvement requested in the issue: Replace console.* usage with project logger for consistent logging #433
• Install pino library to handle logs. pino - npm
• Install pino-pretty to format logs in development mode. pino-pretty - npm
• Adds pino logger configs to api and socket-server
• Replace console.* with logger.* in all files found

Checklist

• I reviewed my PR code before submitting
• I ensured that the implementation is working correctly and did not impact other parts of the app
• I mentioned the PR link in the task

[guimroque]

🟡 IMPORTANT: Unused import removal

Problem:
The FUEL_PROVIDER constant is imported but no longer used after the console.log removal.

Suggestion:
Remove the unused import:

const { API_URL } = process.env;

[pedroanastacio]

FUEL_PROVIDER has been removed: 79c4314

[guimroque]

🟡 IMPORTANT: Inconsistent log message format

Problem:
This log message doesn't follow the structured format pattern used elsewhere. The chain info is concatenated as a string instead of being a separate field.

Suggestion:
Use structured logging format:

logger.info(
  { 
    predicateAddress: addrShort, 
    chainId: chainId ?? 'all',
    operation: 'cache_invalidation'
  },
  '[TX_CACHE] Caches invalidated'
);

[pedroanastacio]

Adjusted on: fe9ab4f

[guimroque]

Code Review - Summary

What was done

This PR implements structured logging using Pino library to replace direct console.* calls throughout the codebase. The changes include:

• Installing pino and pino-pretty dependencies
• Creating comprehensive logger configuration with security-focused data redaction
• Adding ESLint rule to prevent console.* usage (except in scripts/migrations)
• Replacing all console.* calls with structured logger calls across ~40 files
• Implementing proper log levels and structured data logging

Positive Points

• Excellent security compliance: Comprehensive redaction of sensitive data (passwords, tokens, private keys, etc.)
• Production-ready configuration: Different formats for dev (pretty) vs prod (JSON)
• Consistent implementation: Systematic replacement of console calls with proper structured logging
• Good ESLint integration: Prevents future console.* usage while allowing exceptions for scripts
• Proper error context: Most logger calls include relevant context data
• Performance consideration: Non-blocking cache operations with error logging

Issues Found

• 1 Critical: Typo in variable name that could cause runtime errors
• 2 Important: Inconsistent log message formatting and unused import
• 1 Suggestion: Minor formatting improvement opportunity

Total comments: 4 (1 critical, 2 important, 1 suggestion)

[guimroque]

LGTM! ✅

Previous issues have been fixed. Code approved.