chore(431-1): multichain list preparation

[vinnyhoward]

Description

This pull request is preparatory work for the upcoming multi-chain feature, here is the pull request. It introduces utility functions and type improvements to support multi-chain asset management. The improvements for chain id's mapping is also an attempt to mirror what we have in extension

Key Changes

1. Added new utility functions:

   • enableAllNetworksFilter: Creates a mapping of chain IDs to boolean values for network filtering
   • filterAssets: Generic asset filtering utility that supports chain ID and balance filtering

2. Enhanced network type definitions:

   • Updated NETWORK_CHAIN_ID to use readonly properties for better type safety
   • Improved type integration with @metamask/transaction-controller's CHAIN_IDS

3. Added test coverage:

   • Tests for enableAllNetworksFilter covering basic functionality and edge cases
   • Tests for filterAssets demonstrating chain ID and balance filtering capabilities

Technical Details

• enableAllNetworksFilter: Converts network configurations into a boolean map for filtering
• filterAssets: Implements flexible filtering with support for:
  • Inclusive filtering (e.g., specific chain IDs)
  • Range filtering (e.g., token balances)
  • Extensible filter callback system

Purpose

This PR aims to:

1. Reduce the complexity of the main multi-chain feature branch
2. Introduce necessary utilities for multi-chain asset management
3. Improve type safety for network-related operations

Related issues

Fixes: NA

Manual testing steps

1. None

Screenshots/Recordings

NA

Before

NA

After

NA

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 started on Bitrise...🔄🔄🔄

Commit hash: 0066034
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/5454a801-3fbc-4457-83dd-e30b3e5c48c4

Note

• This comment will auto-update when build completes
• 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

[gambinish]

Only nit I would add is to add a comment link to the extension networks, but nbd

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: 894743a
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/f378274b-77ed-4939-9cf3-14669b420b6e

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

Tip

• Check the documentation if you have any doubts on how to understand the failure on bitrise

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud

[vinnyhoward]

Mirror what we have in extension. See here