fix: tokens list to display with hideTokensWithoutBalance setting

[sahar-fehri]

Description

PR to fix an issue with the tokenList showing the msg "You don't have any tokens" when popular networks is selected and the setting HideTokensWithoutBalance is enabled

Related issues

Fixes:

Manual testing steps

1. click on account selector
2. Create a new empty account
3. Go to settings => General and and toggle hide tokens without balance setting
4. go back to home page; and select popular network
5. You should still see native tokens even with zero balance. Only ERC20 tokens should not be displayed when the setting is ON

Screenshots/Recordings

Before

After

Screen.Recording.2025-01-15.at.16.46.55.mov

Pre-merge author checklist

• I’ve followed MetaMask Contributor Docs and MetaMask Mobile 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.

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 4f8b3e4
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/2d9e28c1-eda9-40df-9d8d-79dd47ac35d2

Note

• You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[gambinish]

I'm unsure if this is the expected behavior, and it won't align with the behavior on extension.

I'm flagging this until we come to a decision with Product 👍