…agged

- Introduce BleLoggingConfig (BleLogLevel + BleLogFormat) decoupled from
  Kable's API surface so Koin/test classpaths don't need Kable types.
- Provide via Koin from BuildConfigProvider.isDebug: Events in debug,
  Warnings in release. Format defaults to Compact (single-line) which is
  much friendlier for adb logcat / grep than Kable's default Multiline.
- Inject the config into KableBleConnectionFactory and KableBleScanner
  instead of the previously hard-coded Events/Multiline pair.
- Tag the Android MTU negotiation log with the device address so
  multi-device sessions are unambiguous.
- KoinVerificationTest: declare the wrapping enums as known extra types.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Kable optimization audit improvements (Phase A+B of full audit).

Connection quality:
- Request high connection priority (CONNECTION_PRIORITY_HIGH) right
  after the MTU exchange — meaningful throughput uplift on Android.
- Document the rationale for the LE / 1M PHY default in
  KablePlatformSetup so future tuners know the constraints.

Retry behavior:
- BleRetry now does exponential backoff (factor 2, cap 2000ms) with
  ±25% jitter; default initial delay lowered 500ms→250ms. Avoids
  thundering-herd reconnects after firmware drops.

Reactive surface:
- BleConnection.deviceFlow / connectionState are now StateFlow, with
  distinct-equals semantics. Subscribers get the current value
  immediately on collect — no more missed-edge races on connect.
- FakeBleConnection / CancellingProfileBleConnection updated to match.

Profile / write path:
- Cache toRadioWriteType once per service instead of recomputing per
  packet; halves the property reads on the hot send path.
- Latch triggerDrain to capacity=1 (was 64) — drain is idempotent so
  one pending tick is sufficient.
- Log swallowed logRadio errors at debug instead of silently dropping.

Misc:
- Clarify the autoConnect 'giving up' log message so it's clear we
  fall back to scan-and-connect on Android's autoConnect ceiling.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

- KableBleConnection: when reusing a peripheral, the long-lived stateJob
  observer kept a reference to the MeshtasticBleDevice instance captured
  at the previous connect() call. If the bonded-device cache swapped the
  instance for the same address (e.g. firmware-reported name change),
  every subsequent state transition was dispatched to the stale device,
  leaving the new instance's _state StateFlow stuck at Disconnected.
  Capture the active device in a @volatile field that the observer reads
  on each emission instead.

- BleRetry: drop the hand-rolled pow() shim and use kotlin.math.pow.
  The shim's justifying comment was wrong — kotlin.math.pow is part of
  the common stdlib and is already used elsewhere in commonMain
  (NumberFormatter, LocationUtils, PositionPrecisionPreference).

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

attemptConnection wrapped its disconnect-watcher in
`coroutineScope { onEach{}.launchIn(this); first { Disconnected } }`.
coroutineScope waits for ALL launched children before returning, but a
launched collector on a hot StateFlow never completes naturally. Once
.first returned, the scope hung forever, blocking BleReconnectPolicy
from issuing the next attempt — so a node power-cycle (the canonical
'stable connection then remote drop' path) silently never reconnected.

Replace the coroutineScope wrapper with a plain
`connectionState.filterIsInstance<Disconnected>().first()` and call
onDisconnected() inline. Add a `first { Connected }` gate beforehand
to defeat the StateFlow stale-value race on attempt #2+, where the
previous cycle's Disconnected value would otherwise match immediately.

Add regression test `transport reconnects after a stable connection
is dropped remotely` exercising the full happy-path reconnect cycle,
plus `simulateRemoteDisconnect`/`connectAndAwaitCalls` plumbing on
FakeBleConnection.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

DesktopKoinTest now declares BleLogLevel/BleLogFormat as extraTypes (Koin
Verify introspects the BleLoggingConfig data class constructor even though
the factory builds it from constants), mirroring the Android verifier.

The DFU transport tests' AutoRespondingBleConnection fake now exposes
deviceFlow/connectionState as StateFlow to match the tightened
BleConnection interface.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>