feat(tools): add an interactive console for manually running the library

[kb1ibt]

Adds solixble, an interactive console for finding, connecting to and driving devices by hand, with every frame shown each way in clear text. Based on the paths PR; a separate concern from the protocol work, so it can wait or go independently.

pip install "SolixBLE[cli]"
solixble            # or: python -m SolixBLE
solixble> scan 10
solixble> connect 0
solixble> send 404a PARAMETERS_ON
solixble> console

• scan [secs] lists advertising Anker devices with the advertisement's MAC, product type, sku and capability, and the class device_class_from_advertisement picks; scan [secs] raw adds each device's advertisement as bytes (the 0xffff record, marked when it doesn't parse, other manufacturer data, service data and services), for models whose record isn't known yet. connect <n|mac|address> [class] connects one, as that class or one you name.
• info shows the class, outer protocol, path and the device's announcement; data, props, constants and call <method> [args] (enums by member name) use the device class as HaSolixBLE does.
• send (_send_command), packet (_send_packet on any pattern) and nego (a frame on 030001 under the live session) take a parameter dict as the device modules write it, or a PARAMETERS_* name; '@ts' is the live timestamp. The frames of the next two seconds are printed after each send.
• frames [n] shows every frame, both directions, as cleartext with its status byte and tags. capture <file> appends the whole session to a file, never truncated: the frames, each command and its output, the Python console's input and log records with tracebacks, every line dated. Frames are recorded by a mixin on the connected device's class (FrameTap), not by changing how the library sends or receives.
• --log-level sets SolixBLE's log level and --bleak-log-level bleak's (default warning), so the library's debug output doesn't come with bleak's record per advertisement.
• Two log fixes in device.py, seen in console captures: a requested disconnect() was logged as "came from other client" (the client is disposed of before bleak reports the drop; it now logs "Disconnected from ''."), and the init line read "withaddress". The disconnect callback is annotated with the BleakClient bleak passes it, which clears two mypy errors.
• console opens a Python prompt on the same event loop with the devices in scope and top-level await (stdlib codeop, as python -m asyncio does).
• token / --token sets the client token used in 4027 and as the Prime 420a owner; region / --region calls set_region. Channel 0c (the factory lane) is refused unless started with --allow-factory-channel.

prompt-toolkit is an optional extra ([cli]), so installing the library alone pulls in nothing new; it is in requirements_dev.txt for the tests. Docs: new cli.rst.

Suite: 481 passed (base: 459). mypy --strict: 201 errors (base: 203).

[kb1ibt]

This PR, while based on #80, ports a tool I already used as part of my data collection stack. It acts very similarly to a network switch's serial console or SSH terminal and has an "advanced" mode, console, to drop into a Python REPL with autocomplete for most of the SolixBLE library.