Problem

The AMQP client library was using console as the default logger, which caused issues for applications using structured logging. Random console.log, console.warn, and console.error calls from the library would:

• Break log parsers expecting structured JSON output
• Pollute application logs with unformatted messages
• Make it impossible to control logging behavior from the consuming application

Solution

This PR changes the default logging behavior to be opt-in rather than automatic:

Key Changes

1. Default logger is now undefined instead of console in AMQPBaseClient
2. Added logger parameter to constructors:
   • AMQPClient constructor accepts optional logger parameter
   • AMQPWebSocketClient constructor accepts optional logger parameter
   • AMQPWebSocketClient init object supports logger property
3. Fixed hardcoded console usage - replaced console.info with this.logger?.info for consistency

Usage Examples

// Default: no logging (won't interfere with structured logging)
const client = new AMQPClient('amqp://localhost')

// Opt-in to console logging for debugging
const debugClient = new AMQPClient('amqp://localhost', undefined, console)

// Use custom structured logger (Winston, Bunyan, etc.)
const structuredClient = new AMQPClient('amqp://localhost', undefined, myLogger)

// WebSocket client with logger via init object
const wsClient = new AMQPWebSocketClient({
  url: 'wss://example.com/amqp-ws',
  logger: myLogger
})

Backward Compatibility

• No breaking changes - existing code continues to work unchanged
• All logging calls use optional chaining (?.) so they safely handle null logger
• Same Logger interface - Pick<typeof console, 'debug' | 'info' | 'warn' | 'error'>

Testing

Added comprehensive test coverage:

• ✅ Default logger is undefined
• ✅ Custom logger can be provided via constructor
• ✅ WebSocket client supports logger in both constructor and init object
• ✅ No errors when logger is null
• ✅ Custom logger receives expected calls

Libraries should not log by default unless explicitly configured to do so. This change allows consuming applications to maintain control over their logging strategy while still providing debugging capabilities when needed.

Fixes #143.

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