fix(deeplinks): route a jump link that carries its own path

[bmc08gt]

Two fixes found while testing #1366 after it merged.

A tip card link from the website opened the app and did nothing

"Open in Flipcash" on flipcash.com/<handle> does not navigate to the URL in the address bar. The page's script redirects to a redirector:

const url = `https://jump.flipcash.com/tip/${uuid}`;
window.location.href = url;

classifyOrThrow read jump.flipcash.com as a wrapper and nothing else, so a link with no #source= fragment left unwrapJumpTarget() returning null and fell through to unrouted() — which returns None for every host but the bare flipcash.com. The tap brought the app to the front and nothing happened, from anywhere in the app.

A jump link is now classified by its own path when there is no fragment to unwrap. The redirector is claimed whole by the manifest and mirrors the app's path space, so /tip/{id} resolves the same as it does on app.flipcash.com. A #source= fragment still takes precedence, and isProfileLink stays host-gated to flipcash.com, so the redirector does not start claiming handles.

DeepLinkController on iOS is described as the mirror of this branch, so it likely drops the same URL.

The insufficient-balance prompt drew behind the tip modal

NavMessagingEntryDecorator was nested inside NavBillOverlayEntryDecorator, and the outermost decorator paints last, so the bill overlay covered any prompt raised from it. The two are swapped: a bottom bar message is a prompt that has to be answered, so it sits above what the entry draws.

The in-chat over-balance path also raised a red destructive alert. It now raises the same info prompt the tip card uses, with an "Add Money" action — presentAddMoney still covers the empty account, which has nothing to enter a smaller amount than.