dnstap: don't break request resolution on dnstap errors
This isn't a regression of 5.3.0 changes. Layer functions are supposed to return new values for ctx->state, but here we were sometimes returning kr_error(EFOO) which altered processing of the request.
Our case: answers directly from policy module would not end up finishing the request and we'd hit an assert at the end of processing.