feat: add loading skeleton for staking banners

[amitabh94]

Description

This PR adds a loading component for the time when pooled stakes data is being fetched before being rendered to the user to avoid abrupt pop in of banners on the screen and make the UI experience smoother.

Related issues

Fixes: STAKE-854

Manual testing steps

1. Set export MM_POOLED_STAKING_UI_ENABLED=true in your local .js.env file
2. From the asset list page, click Ethereum
3. You will see a loading skeleton before the staking banners appear.

Screenshots/Recordings

Before

Without_Loading_Skeleton.mp4

After

With_loading_skeleton.mp4

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: e64ab09
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/0ea5fd39-f726-4909-b515-066b1cd57f90

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

[Matt561]

LGTM!

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: b6a4617
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/fcdf65d4-f0d8-4525-a82f-dc6b119d74f5

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

See analysis details on SonarQube Cloud