Bug in new +yaml output when truncation is retried

In testing the code from merge !2168 (merged), I found a new problem. The output is not proper YAML if dig retries due to truncation. For example:

# dig +yaml +nocmd -6 @2001:500:2f::f +notcp . SOA +noadditional +noedns +noauthority +norecurse +time=4 +tries=1
;; Truncated, retrying in TCP mode.
-
  type: MESSAGE
  message:
    type: AUTH_RESPONSE . . .

I suspect that the right answer is just to toss the ";; Truncated, retrying in TCP mode." into /dev/null. Otherwise, you would need to add a new type under "message" called "truncated", with boolean types. That seems like overkill.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information