Description

This PR contains two fixes related to Gas Sponsorship alerts:

• Removes a gas-estimate-related alert for when a transaction will fail in a gasless transaction. Avoids the "double alert" and drops the modal prompting user to change their "gas limit" which doesn't make sense in gasless flows.
• Changes the copy and severity of the specific 10 MON reserve alert - when a tx would bring the balance of the user below the 10 MON minimum imposed by the Monad network - making sure the user is aware when this condition happens and cannot proceed with the tx - which will always fail in those conditions.

Changelog

CHANGELOG entry: remove gas alerts from confirmation modal in gasless flows
CHANGELOG entry: update copy of 10 MON minimal reserve confirmation alert

Related issues

Fixes: https://consensyssoftware.atlassian.net/browse/NEB-951?atlOrigin=eyJpIjoiMDBmNDlhY2E5ZDZiNGQ0NGIwYzNkZGEwMWQ4Y2QxZjYiLCJwIjoiaiJ9

Manual testing steps

Test 1, send MON beyond 10 MON reserve:

On Monad (gas sponsored, but 10 MON reserve limit), try to send:

• Max MON.
• Max MON - 1.
• Max MON - 10.
• Max MON -9.999

Observe that the 10 MON error message is always displayed first, as opposed as before, and that user cannot proceed with the transaction.

Test 2, removal of network fee warnings:

1. On Monad or SEI network, open a transaction confirmation for a transaction that will fail - for example call "pause" on USDC (will fail since you are not admin of the token) -> https://monadscan.com/token/0x754704bc059f8c67012fed69bc8a327a5aafb603#writeProxyContract
2. Observe presence or absence of irrelevant warnings: "Transaction likely to fail" should show up, but not the "Network fee" alert since it is irrelevant in gasless.

Screenshots/Recordings

Before

Failing tx:

Send MON beyond 10 MON reserve:

After

Failing tx:

Send MON beyond 10 MON reserve:

(note: the grayed "Got it" is already flagged as a general separate issue)

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.

Performance checks (if applicable)

• I've tested on Android
  • Ideally on a mid-range device; emulator is acceptable
• I've tested with a power user scenario
  • Use these power-user SRPs to import wallets with many accounts and tokens
• I've instrumented key operations with Sentry traces for production performance metrics
  • See trace() for usage and addToken for an example

For performance guidelines and tooling, see the Performance Guide.

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.

---