fix(peers): don't report unmeasured connections as 1 ms to peer center (#2768)

* fix(peers): don't report unmeasured connections as 1 ms to peer center

A freshly established connection has no latency sample yet, so its
WindowLatency reports 0 and direct_peer_info advertised the peer as
max(1, 0) = 1 ms. With latency_first enabled, every node could then
route through a slow or lossy link until the next report (up to ~60 s),
and a flapping link re-advertised 1 ms on every reconnect.

Skip connections that have no latency sample yet. A peer with no
measured connection is left out of the report; it is reported once its
first sample arrives, because the peer list changes then.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* ci(mobile): use the Android command-line tools build ID

setup-android expects a download build ID, not the displayed tools
version. The value 12.0 becomes 12 and produces a URL that returns 404
when the runner cannot reuse a preinstalled SDK.

Request build 11076708, which provides the same command-line tools
12.0. Keep the runner and other tool versions unchanged.

Validate the workflow YAML and confirm the archive URL returns HTTP 200.

---------

Co-authored-by: imoulei <188999141+imoulei@users.noreply.github.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: KKRainbow <5665404+KKRainbow@users.noreply.github.com>

.github/workflows/mobile.yml

@@ -94,7 +94,7 @@ jobs:
       - name: Setup Android SDK
         uses: android-actions/setup-android@v3
         with:
-          cmdline-tools-version: 12.0
+          cmdline-tools-version: '11076708'
           packages: 'build-tools;34.0.0 ndk;26.0.10792818 platform-tools platforms;android-34 '
 
       - name: Setup Android Environment