fix: route your own tip card to the You tab (deeplink + scan)

[bmc08gt]

Problem

Hitting your own Tip Card did nothing at all — via a /tip/{self} deeplink, or by scanning your own code.

Tipping yourself is a payment no-op, so the flow was correctly disabled — but it was disabled by a bare return in TipCardDelegate.resolveTipCard, after the deeplink or scan had already been consumed. The user is left on whatever screen they were on with no feedback that anything happened.

Both now land on the You tab — AppRoute.Sheets.Menu, the surface that owns your tip card (NavBarRoutes: NavBarButton.TipCard -> Sheets.Menu).

Deeplink

Decided in AppRouter, which gains a currentUserIdProvider wired in RouterModule from the UserManager it already injects. A self-targeted link resolves to DeeplinkAction.Navigate(listOf(AppRoute.Sheets.Menu)) rather than PresentTipCard.

Routing it as a plain Navigate means every existing dispatch site handles it unchanged:

• Cold start — the Navigate branch in MainRoot, where buildNavGraphForLaunch already replaces the launch home with a tab-home deeplink route (you get [Sheets.Menu], not Menu stacked on Wallet).
• Warm — codeNavigator.navigateAll(...) in App.kt, which wraps it as a sheet under v1 and swaps the tab under v2.

Sheets.Menu is already emitted by the router for the my-account email-verification link, so both UI versions are known to handle it.

Scan

Two scan shapes reach this: a QR tip link (Scanner hands the id straight to resolveTipCard) and an OpenCode tip payload (CodeScanDelegate raises TipCardScanned, which the shell routes to the same call). Both funnel through the one guard in TipCardDelegate, so that is where it is answered — it raises TipCardEvent.OwnCardScanned on a new UI-facing flow instead of returning silently, and Scanner collects it and navigates.

tipCardEvents is deliberately separate from TipCardDelegate.events: that channel is the shell's single consumer (consumeAsFlow), this one is the UI's. It is replay-less, so an event raised with no scanner on screen is dropped — correct here, since every producer runs while the scanner is composed.

TipCardOperations is only implemented by TipCardDelegate and RealSessionController delegates to it, so the new member propagates without touching the shell.

Tests

• AppRouterTest — self link resolves to Navigate([Sheets.Menu]); another user to PresentTipCard; a null accountId to PresentTipCard, so a link opened before the account resolves is not swallowed.
• TipCardDelegateTest (new) — own id raises OwnCardScanned and never calls the coordinator; another id resolves and presents as before.