fix (cherry-pick): Handle nullish value in alphanumeric sort

[gambinish]

Cherry-picks 2c72002 to v12.13.0.

Description

Fixes a bug reported where alphaNumeric sort was breaking on .localeCompare method, where it was comparing a null value.

Related issues

Fixes: #30496

Manual testing steps

To replicate the bug

1. checkout main
2. In token-list hard code one of the values in filteredAssets to have a symbol of null. This is the value being passed to the alphaNumeric sort handler, and tokens should be filtered by that value when "Sort by alphanumeric" sort filter is toggled on.
3. App will break with the error posted above.

To check fix

1. Checkout this branch
2. In token-list hard code one of the values in filteredAssets to have a symbol of null. This is the value being passed to the alphaNumeric sort handler, and tokens should be filtered by that value when "Sort by alphanumeric" sort filter is toggled on.
3. Token list should render, app should not break. The token will appear at the top of the list, as an empty string is considered > than an actual value.

Screenshots/Recordings

After

The duplicated 1Inch token is the value I hardcoded for testing purposes.

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.

Description

Related issues

Fixes:

Manual testing steps

1. Go to this page...

Screenshots/Recordings

Before

After

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.

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[metamaskbot]

Builds ready [0992127]

• 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 (1752 ± 64 ms)

Platform	Page	Metric	Min (ms)	Max (ms)	Average (ms)	StandardDeviation (ms)	MarginOfError (ms)
Chrome	Home	firstPaint	395	2152	1684	324	155
		domContentLoaded	1533	2114	1717	128	62
		load	1562	2147	1752	134	64
		domInteractive	16	67	34	13	6
		backgroundConnect	9	74	35	25	12
		firstReactRender	15	93	37	26	13
		getState	4	68	19	18	9
		initialActions	0	1	0	0	0
		loadScripts	1111	1620	1256	119	57
		setupStore	7	60	17	16	8
		uiStartup	1771	2598	2054	200	96

[metamaskbot]

No release label on PR. Adding release label release-12.13.0 on PR, as PR was cherry-picked in branch 12.13.0.