fix(ui): match the iOS number roll in AnimatedNumberText

[bmc08gt]

The Android number roll felt faster and more abrupt than iOS. Frame-by-frame comparison against a 60fps recording of the iOS market cap readout (.contentTransition(.numericText()) with .snappy) showed the difference was mostly in how the digits move together, not the spring speed.

	Before	After
Order	every slot starts on the same frame	left to right, 12ms per position, like iOS
Mid-roll	old glyph gone before new one appears, so the slot goes blank	fades overlap, leaving two dim smudges
Quick scrub	a digit changing every frame restarts from rest and looks held	one spring loop per slot; a change retargets and keeps velocity
Settle	no bounce	damping 0.85, from .snappy's 0.15 bounce
New leading digit	draws over the $ while its slot widens	clipped to the slot's shown width
Blur	cut square at each glyph's edges, visible on the last digit	glyph layers padded by the blur radius

Notes:

• Stiffness stays at 380. It matched iOS's per-digit timing in the recording; a softer spring matching SwiftUI's .default made each digit slower than iOS.
• The stagger applies only to a slot at rest. A slot already rolling retargets immediately, otherwise a scrub would re-delay the right-hand digits every frame.
• The blur fix is needed because Android renders a RenderEffect into a layer the size of its node. Padding the glyph layer by MaxBlur gives the blur room without changing the cell's measured size.
• This changes every AnimatedNumberText: token cards, balance rows, market cap, the explainer, link cards and the amount area.

New tests: digits start left to right and a digit changing every frame still rolls out, both failing before the change.