Connection leak in go-couchbase

On a client CBSE it has been observed that on huge clustered monitoring load (specifically distributing prepared statements), N1QL could end up with loads of connections to localhost:8091.

On code inspection, it transpires that access to the pools and node services is done using an http transport with no idle connection limit and a client with no timeout, meaning that if ns_server doesn't respond quickly enough, go-couchbase could open more and more connections.