GPS info panel shows incorrect status when GNSS is disconnected in Trimble Mobile Manager

Nobody has claimed this yet.

**Description**

When the user manually disconnects GNSS in Trimble Mobile Manager (TMM), the Mergin Maps app should display **"No data"** in the GPS info panel. Instead, the app shows an incorrect status depending on the platform:

1. **Android** — GPS info panel shows **"Connected"** and continues displaying all position data (stale data from before the disconnect)
2. **iOS** — GPS info panel shows **"Disconnected"** with no position data

Neither state correctly reflects the expected "No data" status that should appear when the GNSS feed is intentionally cut in TMM.

**Workaround**

Set the position provider to internal → switch back to Trimble → GPS info panel then shows "No Data" text and the position bubble shows "Connected, no position". This is the correct expected state.

**Steps to reproduce**

1. Open the Mergin Maps app and connect to a Trimble GNSS device via Trimble Mobile Manager
2. Verify the GPS info panel shows position data and "Connected" status
3. In Trimble Mobile Manager, manually disconnect the GNSS (disable the GNSS output)
4. Return to Mergin Maps and observe the GPS info panel

**Actual results**

- **Android:** GPS info panel continues to show **"Connected"** status with all position data (latitude, longitude, accuracy, etc.) — data appears stale/frozen from before the disconnect
- **iOS:** GPS info panel shows **"Disconnected"** with no position data

**Expected results**

GPS info panel should display **"No data"** status on both platforms immediately after GNSS is disconnected in TMM — consistent with the state achieved via the workaround (position bubble: "Connected, no position").

*Conclusion*
*Created by Claude and supervised by a human test analyst.*

Start at the GPS info panel and the Trimble Mobile Manager GNSS connection handling described in the reproduction steps, comparing Android and iOS behavior after GNSS output is disabled. Verify the resulting state against the workaround: both platforms should show "No data" with no stale position values and a "Connected, no position" bubble.

Written by the indexing model from the issue text.