Timeout handler is triggered even when no commands are pending (or timed out)

The timeout handler is triggered even when no commands are pending. Normally the timeout handler is reset when lcb_wait() is invoked, however for SDKs which do not use lcb_wait() [ i.e. node.js ] this will trigger the handler.

Operations are not immediately failed since the failure of the operation is dependent on the actual current time vs the time of the first packet in the queue, however lcb_bootstrap_errcount_incr() is called, eventually triggering a config refresh after a given amount of time.