feat(wallet): Cancel & Speed Up Tx in Tx Status Screen

[nuo-xu]

Resolves brave/brave-browser#41799
Resolves brave/brave-browser#41800

Submitter Checklist:

• I confirm that no security/privacy review is needed and no other type of reviews are needed, or that I have requested them
• There is a ticket for my issue
• Used Github auto-closing keywords in the PR description above
• Wrote a good PR/commit description
• Squashed any review feedback or "fixup" commits before merge, so that history is a record of what happened in the repo, not your PR
• Added appropriate labels (QA/Yes or QA/No; release-notes/include or release-notes/exclude; OS/...) to the associated issue
• Checked the PR locally:
  • npm run test -- brave_browser_tests, npm run test -- brave_unit_tests wiki
  • npm run presubmit wiki, npm run gn_check, npm run tslint
• Ran git rebase master (if needed)

Reviewer Checklist:

• A security review is not needed, or a link to one is included in the PR description
• New files have MPL-2.0 license header
• Adequate test coverage exists to prevent regressions
• Major classes, functions and non-trivial code blocks are well-commented
• Changes in component dependencies are properly reflected in gn
• Code follows the style guide
• Test plan is specified in PR before merging

After-merge Checklist:

• The associated issue milestone is set to the smallest version that the
  changes has landed on
• All relevant documentation has been updated, for instance:
  • https://github.com/brave/brave-browser/wiki/Deviations-from-Chromium-(features-we-disable-or-remove)
  • https://github.com/brave/brave-browser/wiki/Proxy-redirected-URLs
  • https://github.com/brave/brave-browser/wiki/Fingerprinting-Protections
  • https://github.com/brave/brave-browser/wiki/Brave%E2%80%99s-Use-of-Referral-Codes
  • https://github.com/brave/brave-browser/wiki/Web-Compatibility-Exceptions-in-Brave
  • https://github.com/brave/brave-browser/wiki/QA-Guide
  • https://github.com/brave/brave-browser/wiki/P3A

Test Plan:

1. Create either a .ethSend, .erc20Approval, .erc20Transfer, .eth721Transfer or .ethSwap
2. Once the tx is submitted to the chain, you are in the flow of displaying the current tx's status
3. You will see Cancel transaction button enabled once the tx has been submitted
4. Quickly click this button you will see a confirmation screen shows up
5. Click the back button the cancel
6. You might need to repeat step 1 to 4 if your transaction gets confirmed
7. Click Cancel transaction in the confirmation
8. The status screen will be dismissed and a new pending transaction created
9. Click confirm
10. Now you are entering again the tx status flow but for this new transaction
11. Notice there is no Cancel transaction button anymore
12. Let it gets confirmed
13. You will see the confirmed status will display correct message.
14. Go back to Activity tab
15. You will see a transaction that sent 0 ETH is successfully confirmed on chain
16. Create other transaction that is not Eth coin type
17. You will not see the Cancel transaction button in the tx status flow

Cancel button	Confirmation	Activity
Cancellation Tx	Send Tx Cancelled	ERC20Approval Cancelled
ERC20 Tx Cancelled

Speed up a eth tx
For demo purpose the banner will be displayed 1 second after tx status screen is visible. But the actual timer is 5 seconds. If you tx is confirmed or errored out before 5 seconds you won't see the speed up banner
https://github.com/user-attachments/assets/fd653976-db8b-4771-b55b-5291ad710fcd

1. create a ETH tx and confirm it. Please take a glance of the gas fee.
2. once the tx status shows up, wait for the speed up banner to be shown
3. click the speed up button
4. you will see the tx status screen will be dismissed and a new pending tx will be shown and notice that this pending tx's gas fee should be greater than the gas fee in step 1
5. confirm this pending tx
6. tx should get confirmed shortly.

[brave-builds]

Released in v1.75.104