feat(wallet): implement bridge to aurora button

[muliswilliam]

Resolves brave/brave-browser#24377

Submitter Checklist:

• I confirm that no security/privacy review is not needed
• 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. Click on an asset in portfolio list for example Ethereum
2. On the asset details page, if the asset support aurora bridging, you will see a button with the text Bridge to Aurora
3. Click on the button, a modal should appear with bridging details.
4. Click on Open rainbowbridge.app. A new tab should open and load https://rainbowbridge.app

Bridge.to.Aurora.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

[srirambv]

Verification passed on

Brave	1.44.26 Chromium: 104.0.5112.81 (Official Build) nightly (64-bit)
Revision	5b7b76419d50f583022568b6764b630f6ddc9208-refs/branch-heads/5112@{#1309}
OS	Windows 11 Version 21H2 (Build 22000.795)

• Verified steps from PR
• Verified for supported asset, there is a button Bridge to Aurora on the asset details screen
• Verified clicking on the button shows a modal about bridging details
• Verified Learn more opens a new tab page and loads https://ethereum.org/en/bridges/#bridge-risk
• Verified the modal is shown only once for the first time. Subsequent attempts doesn't show the modal

14452.mp4