cherry-pick: Adds confirmation screen for 'increaseAllowance' (#23560)

[pedronfigueiredo]

NOTE: This PR is blocked by changes to core
repo as well as to the test dApp first.

Reuses the token approve confirmation screen for 'increaseAllowance'. It also includes an e2e test for the complete flow.

Fixes:
#2224

1. Go to the test dApp
2. Create a token
3. Approve token for a small amount
4. Try to transfer a higher amount of tokens from another account. (it should fail)
5. Go back to the first account and increase the allowance.
6. Try to transfer again from the second account. (it should succeed)

• I’ve followed MetaMask Coding Standards.

• I've clearly explained what problem this PR is solving and how it is solved.

• I've linked related issues

• I've included manual testing steps

• I've included screenshots/recordings if applicable

• 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.

• I’ve properly set the pull request status:

  • In case it's not yet "ready for review", I've set it to "draft".

• In case it's "ready for review", I've changed it from "draft" to "non-draft".

• 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.

Description

Related issues

Fixes:

Manual testing steps

1. Go to this page...

Screenshots/Recordings

Before

After

Pre-merge author checklist

• I’ve followed MetaMask 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.

[pedronfigueiredo]

@metamaskbot update-policies

[metamaskbot]

Policies updated

[pedronfigueiredo]

@metamaskbot update-policies

[metamaskbot]

Policies updated

[metamaskbot]

Builds ready [874039d]

• builds: chrome, firefox
• builds (beta): chrome
• builds (flask): chrome, firefox
• builds (MMI): chrome, firefox
• builds (test): chrome, firefox
• builds (test-flask): chrome, firefox
• build viz: Build System
• mv3: Background Module Init Stats
• mv3: UI Init Stats
• mv3: Module Load Stats
• mv3: Bundle Size Stats
• mv2: E2e Actions Stats
• code coverage: Report
• storybook: Storybook
• typescript migration: Dashboard
• all artifacts
• bundle viz:

  • background: 0, 1, 2, 3, 4, 5
  • common: 0, 1, 2, 3, 4, 5, 6
  • content-script: 0
  • contentscript: contentscript
  • disable-console: disable-console
  • policy-load: policy-load
  • sentry-install: sentry-install
  • ui: 0, 1, 10, 11, 12, 2, 3, 4, 5, 6, 7, 8, 9

Page Load Metrics (498 ± 406 ms)

Platform	Page	Metric	Min (ms)	Max (ms)	Average (ms)	StandardDeviation (ms)	MarginOfError (ms)
Chrome	Home	firstPaint	71	155	97	21	10
		domContentLoaded	10	53	24	11	5
		load	58	2349	498	846	406
		domInteractive	10	53	24	11	5

Bundle size diffs [🚨 Warning! Bundle size has increased!]

• background: -2.57 KiB (-0.07%)
• ui: 6.56 KiB (0.09%)
• common: 36.17 KiB (0.72%)