Selected network per origin

[darkdh]

Resolves brave/brave-browser#29638
Resolves brave/brave-browser#24414

Recommend reviewing this PR in the sequential commits order.

Muli-chain refactoring is necessary before we allow using different network per origin because current tx components are built on a global selected network per coin basis. The refactor is to make sure we can handle multiple transactions in different networks per coin at the same time.
When dealing with per origin selected network, we need to persist it in kBraveWalletSelectedNetworksPerOrigin which is different than kBraveWalletSelectedNetworks which is what we currently used. And we won't need to migrate kBraveWalletSelectedNetworks because it will still be used when Origin is not available as a fallback option, we call it default network now. Users can change it in brave://settings/wallet/networks or through panel in internal pages like brave://wallet

Desktop UI now also shows chain_id from tx or from request instead of selected network when showing SendTransaction, SignMessage, SignTransaction and SignAllTransactions.

Note that this PR only update desktop UI for supporting selected network per origin and leverage some fine grained chain_id API, Android doesn't get it for free. We make sure the behavior on Android doesn't change after this PR.

Follow-up issues:

• Android Implement selected network per origin (Android) brave-browser#29635
• iOS Implement selected network per origin brave-ios#7225

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 wiki
  • npm run lint, 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/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:

Test different selected network for different dapps

1. Fresh profile and open brave://settings/wallet/networks and check what current default networks are for each coin
2. Navigate to brave.com and open wallet panel, we should see network for EVM is default network
3. Change the network to "Aurora" and reopen the panel, it should still be "Aurora"
4. Navigate to github.com, and open wallet panel, we should see network for EVM is default network
5. Change the network to "Polygon" and reopen the panel, it should still be "Polygon"
6. Navigate to brave.com and check network should be "Aurora"
7. Navigate to github.com and check network should be "Polygon"
8. Navigate to other sites and network should be default network.
9. Navigate to internal wallet page should always be default network.
10. Filecoin and Solana should have same behavior (Note that panel would remember last selected coin)

Change default network in panel

1. Navigate to any brave:// pages.
2. Open wallet panel and change network.
3. Navigate to brave://settings/wallet/networks and default for that coin should be changed.

Different networks for different transactions

1. Navigate to https://metamask.github.io/test-dapp/ and select network to be Goerli.
2. Navigate to 127.0.0.1:8081 (setup from https://github.com/bbondy/eth-manual-tests) and select network to be Sepolia.
3. Connect and accept from both sites.
4. Create transactions from both sites.
5. We can see two transaction requests with different networks in panel.

Selected network should not affect Transaction

1. Navigate to https://metamask.github.io/test-dapp/ and select network to be Goerli
2. Connect and approve and send a legacy transaction
3. We should see the network display is Goerli, dismiss the panel
4. Go to other page that doesn't have Goerli as selected network
5. Open wallet panel and the unapproved transaction should still shows Goerli

Send Transaction

1. Follow steps of Selected network should not affect Transaction
2. And then approve transaction
3. It should show up on Wallet activity as submitted.
4. Wait for a while it should be confirmed.

Add and switch chain

1. Navigate to https://chainlist.org/ and connect
2. Add any chain that is not in wallet yet.
3. Approve the switch request.
4. Open panel and check network.
5. Navigate to other domains, they should not be switched.
6. Navigate to wallet page, it should still be default network.

[mkarolin]

Strings changes ++

[darkdh]

Adding @SergeyZhukovsky for reviewing Fix Android build

[mkarolin]

strings ++

[SergeyZhukovsky]

++ Android part. Do we need to create an issue for Android to pass origin?

[darkdh]

++ Android part. Do we need to create an issue for Android to pass origin?

Already created: brave/brave-browser#29635

[darkdh]

P3ARotationSchedulerTest.ConstellationRotation and AdBlockServiceTest.SubscribeToCustomSubscription failures on macOS are not related to this PR

[wknapik]

Force-merged on request https://bravesoftware.slack.com/archives/C7VLGSR55/p1681950863774719?thread_ts=1681928144.414669&cid=C7VLGSR55