Create DNS resolve tool

[fortuna]

This helps me test things in remote proxies. See the README.

[daniellacosse]

Are there any instances where-tcp wouldn't make sense? Like if we were to add DoH, would this become redundant? I only ask because maybe a better interface would be some kind of enum, so users can't pass in ambiguous states like -tcp -https for example

[fortuna]

You are right, -tcp wouldn't make sense for DoH/DoT. However, for now I'm just considering standard DNS.

I'm building up to something that can support multiple solutions. I'm trying to do it in a way that we can reuse the standard Resolver, so we can piggyback on the standard Dialer (which takes a Resolver). I'm not sure we can use DoH and reuse the standard Dialer, because Resolver is not that configurable, so we may need to reimplement a lot of the Dialer logic to use DoH.

For now, I've decided to punt on those complexities and stick to standard DNS, and we can revisit in a following step.

[fortuna]

I'll note, however, that this implementation supports DoT if we force TCP and add a TLS transport that allows us to set the alpn to dot, since the plaintext wire format is the same as DNS over TCP.

[daniellacosse]

I see, so basically whatever supports DoH would effectively wrap this (as the scope is standard DNS), making my concern that the interface here could later break a non-issue.