Async KV operations do not record decode_duration

Async KV operations do not add decode_duration spans to the parent span because the active parent span is lost. This is because the async task that schedules the request is different from the task that processes the response. We use a dedicated read thread for multiplexing connections and pass the result back via a TaskCompletionSource.

This does not affect KV sync calls, or other HTTP based requests.