(Wallet) Enable Filecoin support flag

[simoarpe]

Resolves brave/brave-browser#30342

Resolves brave/brave-browser#30402

Security review issue https://github.com/brave/security/issues/1321

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:

• Navigate to the Brave Wallet and create a new Filecoin testnet account
• Add Filecoins using a faucet service
• Send a Filecoin amount to a valid Filecoin testnet address
• Verify the unapproved transaction is created
• Approve the transaction
• Navigate to the Accounts section
• Tap on the Filecoin testnet account
• Lookup for the transaction and tap on it
• Verify the link to the blockchain explorer opens correctly

[SergeyZhukovsky]

++

[Pavneet-Sing]

File coin test net send has issue with network, asset, and balance. Desktop has no asset for filecoin test net send, the filecoin test case works?

file-coin-testnet.webm

[simoarpe]

File coin test net send has issue with network, asset, and balance. Desktop has no asset for filecoin test net send, the filecoin test case works?

Thanks, on it!

[supermassive]

minuend

[simoarpe]

Fixed, thanks!

[simoarpe]

@Pavneet-Sing, the issue was related to the logic used to distinguish between network types. Improved the check to distinguish between mainnet and testnet for Filecoins in the commit 4b8c587 (#18881)

Re-requesting a review, thanks!

[simoarpe]

Method removed as duplicate of AssetUtils.getKeyring.