Add support for DNSLink resolution

[spylogsster]

Added an Open in IPFS option for domains that have a TXT record that is prefixed with dnslink=

Resolves brave/brave-browser#13609
Resolves brave/brave-browser#13611

Submitter Checklist:

• Requested security review https://github.com/brave/security/issues/332
• 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:

• Navigate to brantly.eth.link and en.wikipedia-on-ipfs.org, on both you should see Open in IPFS option in address bar only if IPFS mode is local or gateway
• Click by button will open ipns://[domain] url in new tab, if you have any path in url, it should be added as well
• This should work for all domains that have dnslink= in the TXT dns record and x-ipfs-path HTTP header is present
• This should work if page returned code different from OK 200 or failed due to network/DNS
• This must not work in private windows or in Tor windows
• Please note it doesnt work for me of I use Secure DNS "with your current service provider" as there are no available dns serviers. It may be same on your side

[diracdeltas]

to avoid an extra DNS request (at least for users who haven't yet opted into IPFS), i wonder if it's possible to look up this TXT record in the DNS cache instead? maybe https://source.chromium.org/chromium/chromium/src/+/master:net/dns/host_cache.h?q=dns%20cache&ss=chromium ?

[spylogsster]

to avoid an extra DNS request (at least for users who haven't yet opted into IPFS), i wonder if it's possible to look up this TXT record in the DNS cache instead? maybe https://source.chromium.org/chromium/chromium/src/+/master:net/dns/host_cache.h?q=dns%20cache&ss=chromium ?

This cache should be used inside HostResolver, https://source.chromium.org/chromium/chromium/src/+/master:net/dns/host_resolver_manager.h;l=56?q=HostResolverManager&ss=chromium%2Fchromium%2Fsrc,

Added flag to allow cache usage in parameters and changed code to use one resolver instance per tab helper, but in my tests with Wireshark I see DNS requests for same sites anyway. I will check this logic, probably would be better to create a separate issue for this

[bridiver]

I think we're missing some deps here, too. This target has check_includes = false so you have to manually check unfortunately