Handle unexpected spam from CAN while debugging

[JensOgorek]

While debugging the CAN module using can.unmute(), we noticed that there’s a potential risk of locking up the ESP32. If a large number of CAN messages are received within a short period, the logging loop can occupy the thread for too long, triggering a watchdog timeout. This results in the ESP32 requiring a manual reboot.

It might be worth adding a safeguard here, for example:

• Detecting excessive message volume in a short time frame and temporarily suppressing output
• Checking the buffer size before printing/logging
• Introducing a rate limit for the debug output