daemon/tls: fix a double-free for some cases of policy.TLS_FORWARD

The double-free may have happened in some cases when the upstream resolver was stopped while answering a forwarded query. I was reliably reproducing it by running resperf on two kresd instances with one forwarded to the other, and killing the upstream one.