Patch chrome.dns.resolve to support canonical_name flag

Description

Chromium presently supports IP address resolution:

chrome.dns.resolve('www.brave.com', response => {
  console.log(response.address)
})

In order to combat CNAME-trackers, uBO and others are evaluating Firefox’s implementation of the DNS API, which supports passing optional flags:

chrome.dns.resolve('www.brave.com', ['canonical_name']).then( response => {
  console.log(response.canonicalName)
})

There are many other optional flags, but CNAME appears to be the most necessary for now.

Note: Chromium expects a callback as the second argument. Firefox, however, returns a promise.

[pes10k]

@antonok-edm the idea here is that it might be worth exposing for other extensions that might do adblocking in other ways than brave-core does (folks might want to do disconnect or uBO on top of adblock-rust).

I think it’d be a nice to expose the capability to other extensions if it was easy to do, but if its a medium-to-big lift (say, more than 1-2 days work) its prob not worth doing

[hackademix]

FWIW uBlock Origin only even bothers to check for the presence of browser.dns on Firefox. It just assumes it doesn’t exist on Chromium, so it won’t even work out of the box.

https://github.com/gorhill/uBlock/blob/11d24abea01fdb1c7070a2940dfda6e43cfe0c2c/platform/firefox/vapi-webrequest.js#L53

It wouldn’t work anyway: even if uBlock could leverage this API, it couldn’t be useful on Chromium because webRequest there doesn’t support asynchronous responses and dns.resolve() is asynchronous in nature.