feat(wallet): Backed Up Transactions Warning

[Douglashdaniel]

Description

Implemented a Backed Up Transactions Warning

In the case that user has submitted a transaction and the miners are not able to pick it up due to low submitted gas.
This warning will show if a user attempts to create another transaction and the old Submitted one is over 24 hours old.

1. If user chooses too Clear and continue we override the old transaction by setting the nonce of the new Unapproved transaction to the nonce of the old stuck Submitted transaction.
2. If the user chooses to not Clear and continue we treat the new Unapproved transaction as normal.
3. If a user has multiple Unapproved transactions in queue, the first transactions will display the warning with the Clear and continue option. If chosen the next Unapproved transactions will show the same warning with out the Clear and continue option until the first transaction is Confirmed on the blockchain.

Resolves brave/brave-browser#21051

Submitter Checklist:

• I confirm that no security/privacy review is needed, or that I have requested one
• There is a ticket for my issue
• Used Github auto-closing keywords in the PR description above
• Wrote a good PR/commit description
• 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, npm run lint, 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/Custom-Headers
  • 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

• Demo (note: For this demo I set it to show the warning after a Submitted transaction is 30 seconds old, will actually show if a transaction is still returned as Submitted after 24 hours.)

Working.Example.mov

[brave-builds]

A Storybook has been deployed to preview UI for the latest push

[brave-builds]

A Storybook has been deployed to preview UI for the latest push

[brave-builds]

A Storybook has been deployed to preview UI for the latest push

[josheleonard]

LGTM

[brave-builds]

A Storybook has been deployed to preview UI for the latest push

[brave-builds]

A Storybook has been deployed to preview UI for the latest push

[Douglashdaniel]

Closing this PR as invalid since this issue has since been addressed by the backend.