Revert "OPEN-7: Route/latency tools — region wiring, ICE policy, richer region pings"

[zortos293]

Reverts #174

---

Note

Medium Risk
Touches WebRTC connection configuration and region selection/ping behavior, which can affect stream connectivity and latency. Changes are mostly removal/simplification, but regressions are possible for users relying on relay-only ICE or detailed ping diagnostics.

Overview
Reverts the prior route/latency tools work by removing iceTransportPolicy from shared settings/types, the renderer settings UI, and the GfnWebRtcClient RTCPeerConnection configuration.

Simplifies region latency probing: main process PING_REGIONS now runs 3 TCP connect samples and returns only an averaged pingMs (dropping min/max/jitter/sample metadata), and the settings page ping cache/UI is updated accordingly (including removing jitter display).

Also simplifies streaming base URL derivation to always use the selected provider’s streamingServiceUrl, and updates package-lock.json metadata/version fields.

^{Written by Cursor Bugbot for commit 9c30b5c. This will update automatically on new commits. Configure here.}

[linear]

Issue reopened: OPEN-7 try to add a thing like exitlag lagofast

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

[cursor]

Region selection no longer affects routing

Medium Severity

effectiveStreamingBaseUrl now always uses selectedProvider.streamingServiceUrl and ignores settings.region. The Region picker in SettingsPage.tsx still lets users choose specific regions, but that value is no longer applied when calling streaming APIs, so manual region selection silently has no effect.