refactor: support non-evm tokens in asset-picker

[micaelae]

Description

The main goal of this PR is to enable displaying non-evm tokens and their balances in the AssetPicker. The general approach is to find instances in which components and hooks read evm-specific data and replace them with multichain equivalents

In addition to that, this enables networks that use CAIP chainIds to be selectable in the asset-picker

Changes

• types: allow non-hex chainId values
• asset-picker-modal: show non-evm tokens that have balances
• AssetList.tsxm asset-picker: read currency and account balance info from multichain selectors
• Asset.tsx: read token data from props instead of getTokenList selector
• token-list-item: only parse chainId as in if it's a hex value
• useMultichainBalances: calculate token balances for non-evm tokens and include them in resulting sorted list
• multichain.ts: add a placeholder network configuration for solana

Related issues

Fixes:

Manual testing steps

1. Set BRIDGE_USE_DEV_APIS=1 in .metamaskrc
2. Swap + Send flow should still work for EVM chains
3. Bridge flow should still work when bridging EVM -> EVM

Screenshots/Recordings

Before

After

Screen.Recording.2025-02-25.at.11.42.25.AM.mov

Pre-merge author checklist

• I've followed MetaMask Contributor Docs and MetaMask Extension Coding Standards.
• I've completed the PR template to the best of my ability
• I’ve included tests if applicable
• I’ve documented my code using JSDoc format if applicable
• I’ve applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

[metamaskbot]

Builds ready [e1c1d5c]

• builds: chrome, firefox
• builds (flask): chrome, firefox
• builds (MMI): chrome
• builds (test): chrome, firefox
• builds (test-flask): chrome, firefox
• build viz: Build System
• mv3: Bundle Size Stats
• mv2: E2e Actions Stats
• storybook: Storybook
• typescript migration: Dashboard
• all artifacts
• bundle viz:

  • background: 0, 1, 2, 3, 4, 5, 6, 7
  • common: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13
  • ui: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12
  • content-script: 0
  • offscreen: 0

Page Load Metrics (1719 ± 68 ms)

Platform	Page	Metric	Min (ms)	Max (ms)	Average (ms)	StandardDeviation (ms)	MarginOfError (ms)
Chrome	Home	firstPaint	369	1882	1632	312	150
		domContentLoaded	1480	2061	1692	138	66
		load	1489	2066	1719	141	68
		domInteractive	26	120	48	26	13
		backgroundConnect	9	72	27	19	9
		firstReactRender	15	89	47	26	13
		getState	4	69	20	22	11
		initialActions	0	1	0	0	0
		loadScripts	1026	1608	1233	135	65
		setupStore	8	12	9	1	1
		uiStartup	1683	2450	1961	167	80

Bundle size diffs [🚨 Warning! Bundle size has increased!]

• background: 0 Bytes (0.00%)
• ui: 785 Bytes (0.01%)
• common: 822 Bytes (0.01%)

[metamaskbot]

Builds ready [da1c4e5]

• builds: chrome, firefox
• builds (flask): chrome, firefox
• builds (MMI): chrome
• builds (test): chrome, firefox
• builds (test-flask): chrome, firefox
• build viz: Build System
• mv3: Bundle Size Stats
• mv2: E2e Actions Stats
• storybook: Storybook
• typescript migration: Dashboard
• all artifacts
• bundle viz:

  • background: 0, 1, 2, 3, 4, 5, 6, 7
  • common: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13
  • ui: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12
  • content-script: 0
  • offscreen: 0

Page Load Metrics (1824 ± 71 ms)

Platform	Page	Metric	Min (ms)	Max (ms)	Average (ms)	StandardDeviation (ms)	MarginOfError (ms)
Chrome	Home	firstPaint	321	2131	1745	358	172
		domContentLoaded	1551	1973	1784	135	65
		load	1580	2141	1824	149	71
		domInteractive	28	144	48	31	15
		backgroundConnect	13	172	43	35	17
		firstReactRender	15	78	29	20	10
		getState	6	81	30	26	13
		initialActions	0	1	0	0	0
		loadScripts	1088	1526	1330	124	60
		setupStore	8	69	17	15	7
		uiStartup	1765	2471	2087	178	85

Bundle size diffs [🚨 Warning! Bundle size has increased!]

• background: 0 Bytes (0.00%)
• ui: 785 Bytes (0.01%)
• common: 822 Bytes (0.01%)

[metamaskbot]

Builds ready [da3158b]

• builds: chrome, firefox
• builds (flask): chrome, firefox
• builds (MMI): chrome
• builds (test): chrome, firefox
• builds (test-flask): chrome, firefox
• build viz: Build System
• mv3: Bundle Size Stats
• mv2: E2e Actions Stats
• storybook: Storybook
• typescript migration: Dashboard
• all artifacts
• bundle viz:

  • background: 0, 1, 2, 3, 4, 5, 6, 7
  • common: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13
  • ui: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12
  • content-script: 0
  • offscreen: 0

Page Load Metrics (1487 ± 50 ms)

Platform	Page	Metric	Min (ms)	Max (ms)	Average (ms)	StandardDeviation (ms)	MarginOfError (ms)
Chrome	Home	firstPaint	1362	1737	1490	107	51
		domContentLoaded	1326	1721	1466	110	53
		load	1362	1735	1487	104	50
		domInteractive	23	75	34	18	8
		backgroundConnect	8	67	29	19	9
		firstReactRender	13	65	21	17	8
		getState	4	57	15	16	8
		initialActions	0	1	0	0	0
		loadScripts	955	1261	1065	89	43
		setupStore	7	52	12	12	6
		uiStartup	1553	1958	1688	112	54

Bundle size diffs [🚨 Warning! Bundle size has increased!]

• background: 0 Bytes (0.00%)
• ui: 785 Bytes (0.01%)
• common: 822 Bytes (0.01%)

[gambinish]

Pulled down and tested these:

1. [flask] When navigating to swaps, I see SPL tokens to choose from to create my swap pair
2. [flask] When navigating to bridge, I see SPL tokens to choose from to create my bridge pair
3. Swap/Bridge flows work as expected on evm

[darkwing]

Do we have a constant for token?

[darkwing]

Approving with a bunch of nits I hope we can potentially address.