TCP Retry implementation

[nil0x42]

As most DNS resolvers, an answer with TC=1 (truncated response) should retry with TCP.
From now, TCP fallback is not implemented on DNSanity.

Here is the workflow i'm thinking of:

1. Get answer
2. If matches template entry, no need to TCP fallback, EVEN if TC=1
3. On mismatch & TC=1, fallback to TCP

Now, should it consider the TCP retry as a 'next-try' (counted in max-attempts), or within ResolveDNS itself ?
Another option would be to dynamically increment current check's max-attempts when we need to TCP retry, and set a 'TCP' bool to true, so we know that a TCP request must be performed at next try.