feat: Add max value refresher for transfer redesigned confirmations

[OGPoyraz]

Description

This PR aims to add max value refresher hook into transfer confirmations.

Essentially hook is updating transaction value via updateEditableParams. After design discussions - every update should pulse the TokenHero component. Hence this PR also moves animated-pulse component in to UI components and re-use that.

Regarding changes in animated-pulse: it appears if isPulsing changing too fast it stops animation. Hence there are modifications in animated-pulse component but it's basically making sure pulse animation at least done twice.

Related issues

Fixes: https://github.com/MetaMask/MetaMask-planning/issues/4797

Manual testing steps

Only possible to test it out via setting FEATURE_FLAG_REDESIGNED_TRANSFER to true

Screenshots/Recordings

Before

After

max.value.update.pulse.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]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: e6f9a52
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/07ab2712-0537-45e4-a570-201176277575

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: 9366295
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/7012197a-6b31-45db-8066-6296387a8430

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

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 87.05882% with 11 lines in your changes missing coverage. Please review.

Project coverage is 68.72%. Comparing base (5113000) to head (b4414ef).
Report is 40 commits behind head on main.

Files with missing lines	Patch %	Lines
...ns/components/UI/animated-pulse/animated-pulse.tsx	80.48%	6 Missing and 2 partials ⚠️
...text/confirmation-context/confirmation-context.tsx	81.81%	1 Missing and 1 partial ⚠️
.../Views/confirmations/hooks/useMaxValueRefresher.ts	95.65%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #15074      +/-   ##
==========================================
+ Coverage   68.46%   68.72%   +0.26%     
==========================================
  Files        2372     2384      +12     
  Lines       51275    51517     +242     
  Branches     7634     7683      +49     
==========================================
+ Hits        35103    35405     +302     
+ Misses      13942    13860      -82     
- Partials     2230     2252      +22     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[github-actions]

Bitrise

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

Commit hash: dc08bc9
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/dc657932-09e6-4136-b78f-08d711bb4cc7

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

Commit hash: b4414ef
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/eeff78d8-02f8-4941-a260-58867842ba1b

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: 0e6fbda
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/0559d6c1-590c-4f76-98b5-67ab66f04acd

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
2 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud