Feature request: Auto-reconnect when Bluetooth drops

As a bunch of us start using MP with Dragonlink v3 and its fully bidirectional telemetry, the issue of Bluetooth disconnect headaches has come up. The connectivity between MP on laptop or tablet and the DLA transmitter is via Bluetooth, and generally works well, until you and your radio walk more than ~30 feet from your MP platform. Would it be possible to add some logic to MP where it will attempt reconnection if dropped without explicit user command to disconnect? And when auto-reconnecting, ideally continue with the same log files, and recognize that a full download of the params is unlikely to be necessary. Perhaps checksum compare with ArduPilot on current state of params?

Start by locating Mission Planner’s Bluetooth connection handling, then trace how log files and parameter downloads are managed after a connection is established. Define the reconnection behavior for an unexpected drop, including preserving the current log and avoiding an unnecessary full parameter download; the issue names no files or tests to run.

Written by the indexing model from the issue text.