chore: update and fix bugs in asset-picker network modal

[micaelae]

Description

Change	Before	After
NetworkListItem + AssetPickerModalNetwork add shouldDisableNetwork prop that determines whether a visible network should be selectable	N/A	Figma: dest network picker
AssetList fix: duplicate component keys cause unexpected search behavior when there are multiple tokens with the same symbol
AssetList hide native asset balance when displaying tokens for an inactive network and prevents wrapping balance line
AssetPickerModal isTokenListLoading prop displays a loading overlay until the token list is available. The cross-chain swaps experience fetches token lists from the bridge-api, which can take a few seconds after changing the network. Without a loading screen, the user is able to select a token from the previously selected network, which may be invalid in the new network	WLD does not exist in the avalanche network but is selected: Video	Video
AssetPickerModal change the network picker label to default to NETWORK_TO_NAME_MAP instead of the network name for consistency
AssetPickerModalNetwork add header prop for displaying a custom header and implement search functionality
AssetPicker add a prop for overriding the AssetPicker trigger button with a different component		bridge asset picker button

Related issues

Fixes: N/A

Manual testing steps

The network picker changes can only be tested locally and if other cross-chain swaps changes are pulled into the branch. The only change that could affect the Swap+Send experience is fixing the AssetList keys

1. Select Polygon as the wallet's network
2. Open Send experience
3. Click on src token
4. Search for "CSM"
5. Verify that only 2 CSMATIC tokens appear and console errors related to keys are no longer visible

Screenshots and Recordings

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 [2eb3e4c]

• builds: chrome, firefox
• builds (beta): chrome
• builds (flask): chrome, firefox
• builds (MMI): chrome, firefox
• builds (test): chrome, firefox
• builds (test-flask): chrome, firefox
• build viz: Build System
• mv3: Background Module Init Stats
• mv3: UI Init Stats
• mv3: Module Load Stats
• mv3: Bundle Size Stats
• mv2: E2e Actions Stats
• code coverage: Report
• storybook: Storybook
• typescript migration: Dashboard
• all artifacts
• bundle viz:

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

Page Load Metrics (1858 ± 80 ms)

Platform	Page	Metric	Min (ms)	Max (ms)	Average (ms)	StandardDeviation (ms)	MarginOfError (ms)
Chrome	Home	firstPaint	1665	2294	1863	167	80
		domContentLoaded	1627	2214	1824	151	72
		load	1665	2295	1858	166	80
		domInteractive	17	74	44	17	8
		backgroundConnect	7	79	33	26	12
		firstReactRender	53	117	97	15	7
		getState	4	23	10	6	3
		initialActions	0	1	0	0	0
		loadScripts	1160	1558	1332	115	55
		setupStore	5	59	16	18	9
		uiStartup	1830	2609	2065	186	89

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

• background: 0 Bytes (0.00%)
• ui: 1.51 KiB (0.02%)
• common: 50 Bytes (0.00%)

[darkwing]

When would we not require a network here?

[micaelae]

When the cross-chain swaps experience is initially loaded a network won't be set for the destination (Bridge to) asset picker: https://www.figma.com/design/IuOIRmU3wI0IdJIfol0ESu/Cross-Chain-Swaps?node-id=159-28072&m=dev

[metamaskbot]

Builds ready [b22c344]

• builds: chrome, firefox
• builds (beta): chrome
• builds (flask): chrome, firefox
• builds (MMI): chrome, firefox
• builds (test): chrome, firefox
• builds (test-flask): chrome, firefox
• build viz: Build System
• mv3: Background Module Init Stats
• mv3: UI Init Stats
• mv3: Module Load Stats
• mv3: Bundle Size Stats
• mv2: E2e Actions Stats
• code coverage: Report
• storybook: Storybook
• typescript migration: Dashboard
• all artifacts
• bundle viz:

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

Page Load Metrics (1951 ± 91 ms)

Platform	Page	Metric	Min (ms)	Max (ms)	Average (ms)	StandardDeviation (ms)	MarginOfError (ms)
Chrome	Home	firstPaint	515	2467	1884	369	177
		domContentLoaded	1671	2410	1910	178	85
		load	1680	2495	1951	190	91
		domInteractive	26	77	51	18	9
		backgroundConnect	7	92	45	24	11
		firstReactRender	53	297	112	63	30
		getState	4	93	23	24	12
		initialActions	0	0	0	0	0
		loadScripts	1175	1741	1394	139	67
		setupStore	6	56	12	13	6
		uiStartup	1884	2741	2187	238	115

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

• background: 0 Bytes (0.00%)
• ui: 1.65 KiB (0.02%)
• common: 98 Bytes (0.00%)

[gambinish]

LGTM.

We'll have some conflicts on the Multichain AssetList, but I can address them there.