Support resolution of unstoppable domains with IPFS records via Ethereum

[yrliou]

Resolves brave/brave-browser#15158

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

Test Plan:

1. Go to settings, open drop-down of ENS resolve method settings, should not have Ethereum.
2. Change resolve method of Unstoppable Domains to Ethereum
3. Go to brave://settings/ipfs, set the method to resolve to Gateway
4. Visit brave.crypto, the page should be loaded normally via IPFS.

[iefremov]

not really clear: "many" of what? and the method doesn't explain anything

[iefremov]

also curious whether we consider the endpoint as trustworthy.. In theory, we'd better to follow Rule of 2: https://chromium.googlesource.com/chromium/src/+/master/docs/security/rule-of-2.md
probably something to consider during sec review

[yrliou]

It's calling getMany function defined by Unstoppable Domains's ProxyReader smart contract.

[yrliou]

We issue these calls to Unstoppable Domains smart contract via Infura to the Ethereum network.

[yrliou]

Added some more comments in 1cdb4f081decc67ac46ac53ed9bee83fcf3ebb34, and created security review issue.

[iefremov]

we probably need a security review?

[iefremov]

the code looks fine, but we have to be more verbose, so people external to the project could understand it

[mkarolin]

chromium_src change LGTM

[iefremov]

Thanks @yrliou , much appreciated :D

[yrliou]

unrelated post-init failure in audit-dep.