fix: filter token activity when clicking on native token

[sahar-fehri]

Description

This PR filters out token related activity from activity list when clicking on a native token.

Related issues

Fixes: #6164

Manual testing steps

1. Create an ERC20 token
2. Add the new token to your wallet
3. Send some tokens to another wallet
4. Send ETH to another account
5. Click on the native token and scroll down to see activity, you should not see ERC2O related activity
6. Click on the token; you should see the activity related to token

Screenshots/Recordings

Before

Screen.Recording.2024-12-19.at.14.08.30.mov

After

Screen.Recording.2024-12-19.at.14.04.05.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 failed on Bitrise! ❌❌❌

Commit hash: f04c0f4
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/8f7fcff5-8483-40dd-bf65-a6a50b0cb998

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

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: 709bc8e
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/4a938595-83ff-4abe-8cc1-7b1b57006630

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

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 4d7622b
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/b6ffcd7e-651c-4a2b-b453-9fe8e9cf21ad

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

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 9d83ffb
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/964e1fcc-ba59-48a8-8370-10c15e43a943

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
62.5% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[tommasini]

LGTM