Handle Node.js Debug Messages and Improve Port Termination

[Dacello]

Overview

This PR addresses two issues with Node.js communication:

1. Node.js Debug Messages: Fixes "unexpected message in handle_info/2" errors when Node.js emits debugging information (like "Debugger listening on ws://..." messages).

2. Terminal Reset Safety: Adds error handling around port operations during termination to prevent crashes when ports are in an invalid state.

Implementation Details

• Added a proper handle_info/2 callback to handle messages from Node.js processes
• Implemented a debug_mode configuration option that controls whether Node.js stdout/stderr messages are logged
• Added safeguards to reset_terminal/1 to gracefully handle invalid ports during termination
• Added comprehensive tests to validate both fixes

Usage

When working with Node.js applications that emit debug output:

# In config/dev.exs:
config :nodejs, debug_mode: true

Benefits

• More stable operation in development environments using Node.js debugging tools
• Prevents log flooding by making debug message logging configurable
• Improves robustness during application shutdown
• No breaking changes to existing APIs

Original Contribution

This PR builds on the work by @francois-codes, with refinements to follow best practices for configuration handling and error management.

[Dacello]

Added try/rescue to fix crashes when ports are closed during termination. Instead of blowing up with ArgumentError, we now just log and move on. This helps during dev reloading or when containers are shutting down - basically anytime processes are killed unpredictably.