Added Logging Handler Names & windows pytest support

[shukari]

It is now possible to set loglevels for each module or for all per:

# all loggers
logging.getLogger('meshtastic').setLevel(logging.DEBUG)

# only ble_interface
logging.getLogger('meshtastic.ble_interface').setLevel(logging.DEBUG)

• test are now runable on windows, some are ignored and a fake termios for the decorators
• test_exit_with_exception with a true exception

[Copilot]

Pull Request Overview

This PR introduces structured logging with module-specific handlers throughout the Meshtastic codebase. The main purpose is to enable granular log level control for individual modules or the entire library.

• Adds named logger instances to all modules using logging.getLogger(__name__)
• Replaces direct logging.* calls with module-specific logger.* calls
• Enables per-module log level configuration as described in the PR description

Reviewed Changes

Copilot reviewed 12 out of 12 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
meshtastic/util.py	Adds module logger and converts logging calls
meshtastic/tunnel.py	Adds module logger and converts logging calls
meshtastic/test.py	Adds module logger and converts logging calls
meshtastic/tcp_interface.py	Adds module logger and converts logging calls
meshtastic/stream_interface.py	Adds module logger and converts logging calls
meshtastic/serial_interface.py	Adds module logger and converts logging calls
meshtastic/remote_hardware.py	Adds module logger and converts logging calls
meshtastic/node.py	Adds module logger and converts logging calls
meshtastic/mesh_interface.py	Adds module logger and converts logging calls
meshtastic/ble_interface.py	Adds module logger and converts logging calls
meshtastic/main.py	Adds module logger and converts logging calls
meshtastic/init.py	Adds module logger and converts logging calls

[ianmcorvidae]

Looks pretty reasonable to me skimming from my phone; I'll throw copilot at it for now and set off CI, and try to give it a close look when I've next got a small block of time at a proper computer just in case there's anything finicky to spot. Thanks for the PR!

[shukari]

@ianmcorvidae because the test test_exit_with_exception didnt raise a true exception, the test failed. I changed it and it should now report the traceback. Also i did some changes that windows users can run the tests (some are linux only atm)

[shukari]

So.... i did a pytest and a pylint... please... be ok now 😅