Performance: feat - token options memoization

[JohnathanWhite]

Issue

Seven screens each built the merged token map inline inside useAppSelector:

useAppSelector(({WALLET}) => ({
  ...BitpaySupportedTokenOptsByAddress,
  ...tokenOptionsByAddress,
  ...WALLET.customTokenOptionsByAddress,
}))

useSelector runs on every store dispatch, so this spread a multi-thousand-key object on every dispatch, for every mounted instance. And because the result was always a fresh reference, the equality check could never bail — so the component
re-rendered on every dispatch too. Worst on the 1,500–1,900 line KeyOverview/AccountDetails screens and on per-row components (ContactIcon, MultipleOutputsTx).

A shared useTokenOptionsByAddress hook now selects only the custom-token map (a stable reference) and merges in useMemo, so the identity stays stable until the inputs actually change.

Also fixes a bug: ContactIcon spread the const it was declaring instead of the context value, so the 1inch token map was silently dropped there. eslint had been flagging the unused binding.

Second commit applies the hook to GlobalSelect and cleans up its render path: it walked the entire token registry and ran ~8 sequential wallet filter passes bare in the render body, so all of it re-ran on every search keystroke and every
modal toggle. That's now memoized, it selects one WALLET field instead of the whole slice, and its two FlashLists key on stable ids instead of array indices (index keys over filtered, changing data break recycling and can reuse a row for the
wrong wallet).

How to test

1. Token icons and names resolve correctly on KeyOverview, AccountDetails, KeySettings, Add Custom Token, transaction detail with multiple outputs, and the contacts list. Some icons may now appear where a generic fallback showed before —
   that's the ContactIcon fix, not a regression.
2. Open the wallet/coin picker: type quickly in search, toggle chain filters, scroll. Rows must show the correct wallet — a wrong-row or duplicated row would indicate a list-key problem.
3. Add a custom token and confirm it still appears everywhere it should.
4. Send and swap flows still resolve token metadata correctly.

[gabrielbazan7]

Follow-up to 1903baa and 40ee652: JohnathanWhite#6

[gabrielbazan7]

Already implemented here: #2241. We can close this one.