feat: add staked ETH to metamask mobile homepage and account list menu

[nickewansmith]

Description

1. What is the reason for the change?

We want to be able to view the Staked Ethereum balance on the homepage and have the balance totals update to reflect this

2. What is the improvement/solution?

This PR adds the ability for the metamask-mobile app to view the Staked Ethereum asset balance in the mobile homepage in the Token List while linking to the ETH Asset Detail view. It also adds Staked Ethereum to the homepage total balance and the Account List menu total balances as well. The functionality is gated behind the MM_POOLED_STAKING_UI_ENABLED flag.

Related issues

Closes: https://consensyssoftware.atlassian.net/browse/STAKE-817

Manual testing steps

1. First launch the mobile application with MM_POOLED_STAKING_UI_ENABLED="true" in js.env
2. The homepage should show the Staked Ethereum asset balance for selected account in the homepage even if the balance is 0
3. On mainnet, the percentage +/- of the asset should be listed and should be the same as ETH
4. On holesky, the percentage +/- of the asset should not be listed
5. On an unsupported network, the Staked Ethereum asset should not show at all
6. If you click the Staked Ethereum asset it should go to the ETH asset detail page as Staked ETH is not a real token
7. On the ETH asset detail page, the Staked Ethereum balance should be the same as the homepage, there should be no discrepancy
8. Staking flow should not be affected
9. Total balance on the homepage should include Staked Ethereum balance
10. Total balances per account on the Account List menu dropdown should also include Staked Ethereum balance
11. All balanced mentioned should update when there is a balance change, one can go through staking flow to test this
12. There should be no discrepancies across amounts as they have been addressed

Screenshots/Recordings

Before

WIP

After

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.

[nickewansmith]

I have read the CLA Document and I hereby sign the CLA

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: a1ffc42
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/c1e3adbf-bb1b-4a8d-9963-f72ccb8411a7

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 failed on Bitrise! ❌❌❌

Commit hash: e3d4b1f
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/285717b5-c35a-4d45-a8ab-36d913c750a4

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: b1b16c7
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/c2c1fb77-8d52-4a3a-a2bc-9779dae0a0e8

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

[amitabh94]

Some minor comments but otherwise LGTM!

[github-actions]

Bitrise

🔄🔄🔄 pr_smoke_e2e_pipeline started on Bitrise...🔄🔄🔄

Commit hash: 16c6e6f
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/1b1d19a6-0096-4e45-8118-93fa31e63de4

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

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 46615fc
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/2fa96487-8a6d-456a-b4d7-16da180c7f8a

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

[sonarcloud]

Quality Gate passed

Issues
6 New issues
0 Accepted issues

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

See analysis details on SonarCloud

[chrisleewilcox]

LGTM