fix(wallet): ERC721 Refresh after Success Response

[Douglashdaniel]

Description

Refreshes your Portfolio balances upon a Success response for adding an ERC721 token.

Resolves brave/brave-browser#25578

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

Test Plan:

1. Add a Custom NFT and click Add and Done
2. You NFT should eventually show up in your Portfolio

Before:

Screen.Recording.2022-09-27.at.11.58.58.AM.mov

After:

Screen.Recording.2022-09-27.at.11.49.40.AM.mov

[brave-builds]

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

[onyb]

++

[srirambv]

Verification passed on

Brave	1.46.66 Chromium: 107.0.5304.36 (Official Build) nightly (64-bit)
Revision	2f9c7a5a1fe357d87e9bc07c65cca9136b3651c5-refs/branch-heads/5304@{#671}
OS	Windows 11 Version 22H2 (Build 22623.746)

• Verified steps from PR and issue description
• Verified added NFT is shown automatically under portfolio without having to refresh the portfolio page

15241.mov