feat: enable audio playback for dashboard route clips

[Mahdi451]

Summary

• add an explicit mute/unmute control to the dashboard route video player
• keep autoplay browser-safe by starting clips muted and re-muting on route changes
• add a browser test covering the unmute flow

Problem

Dashboard route clips in new-connect always played muted because the player hard-coded the HTML5 muted attribute and provided no way for the user to reverse it.

Fix

• move mute into local player state instead of a permanent attribute
• add a speaker toggle to the existing overlay controls
• preserve autoplay compatibility by keeping initial playback muted
• catch interrupted play() promises to avoid noisy abort errors during route switches and tests

Testing

• bun run test src/App.browser.test.tsx --run
• manual local check at http://localhost:3000/
• verified the clip starts muted, unmute enables audio, and route changes start muted again

Closes #615

[github-actions]

Changes:

path	lines	diff
./map/geocode.spec.ts	134	+105
./components/RouteVideoPlayer.tsx	214	+26
./map/geocode.live.spec.ts	18	+18
./App.browser.test.tsx	44	+4

Total lines: 4891 (+153)

[github-actions]

deployed preview: https://616.connect-d5y.pages.dev

Welcome to connect! Make sure to:

• read the contributing guidelines
• mark your PR as a draft until it's ready to review
• post the preview on Discord; feedback from users will speedup the PR review

Mobile

Desktop

[Mahdi451]

The failing test check does not appear to be caused by this audio PR.

Evidence:

• the PR only changes RouteVideoPlayer.tsx, Icon.tsx, and App.browser.test.tsx
• the new browser test in src/App.browser.test.tsx passed in CI
• the failing test is src/map/geocode.spec.ts, which hits live reverse-geocoding data and is unrelated to the dashboard video player

Locally:

• bun run test src/App.browser.test.tsx --run passes
• bun run test src/map/geocode.spec.ts --run fails independently

This looks like a separate flaky or externally dependent geocoding test issue rather than a regression from the audio change.

[Mahdi451]

Following up on the earlier unrelated CI failure mentioned here: that issue was addressed separately in #617.

That follow-up PR stabilizes the geocode tests and also fixes the GitHub Actions test job timeout/cancel behavior that was causing confusing red checks outside the audio change itself.

[Mahdi451]

Pausing this PR for now so the geocode/test stabilization can be reviewed and merged separately in #617. Once #617 lands, I'll clean this branch back down to the audio-only change and resume review here.

[Mahdi451]

Closing this in favor of the fork-owned integration PR: Mahdi451#1 . The combined branch includes the route audio work plus the fork preview changes that will be validated in that preview.