fix: support for batch of signature requests

[vinistevam]

Description

This PR addresses the issue of multiple signature popups being triggered sequentially on Mobile, which could lead to potential spam or overwhelm the user. Currently, multiple signature requests appear one after the other, even if the user accepts or rejects them. To align with the existing behavior for transactions, this PR removes signatures from the rate-limiting exclusions, ensuring that only one signature request is triggered at a time, preventing spam-like behavior until a proper queuing system is introduced on Mobile.

Related issues

Fixes: #8771

Manual testing steps

1. go to the test dapp
2. connect mm
3. trigger signature x10 batch
4. See you need to accept/reject 1 time

Screenshots/Recordings

sign.one.webm

Example of the current behaviour of batch 10 transactions:

transaction.one.webm

Before

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.

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: 41a343a
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/8a90e9dd-2c1b-4414-8f49-f00e55e18f6d

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: 459945c
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/fa273372-813a-4c05-84f3-ba667d0bcc06

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

All modified and coverable lines are covered by tests ✅

Project coverage is 54.34%. Comparing base (b0ef1a7) to head (7f0ecf0).
Report is 27 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #11729      +/-   ##
==========================================
+ Coverage   54.27%   54.34%   +0.07%     
==========================================
  Files        1711     1714       +3     
  Lines       38712    39102     +390     
  Branches     4738     4843     +105     
==========================================
+ Hits        21010    21250     +240     
- Misses      16253    16367     +114     
- Partials     1449     1485      +36     

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

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarCloud