[client-v2] Resource release

[chernser]

Description

Recently we have found that while using queryRecords leads to error when user forget to close Records object what leads to a connection leaking. We need to review and put some guard rails even this a misuse problem.

We need to:

• Think about detecting orphan response objects somehow
• We need to put more information into ConnectionRequestTimeoutException because it indicates that pool is empty
• We need to review Insert/Command operation code to make sure resource are release as soon as they can.

[chernser]

Triage
There are operations like execute and insert that do not need to read from response body. Once data is sent by user only confirmation is needed. Client gets this confirmation at the end of request or when server sends headers. Task here is to close in/out and release connection.
HTTP transport is problematic at this case because server response can be at the end of data transfer (if there is not much data) or at the middle of transfer when server responded but data still poured into output stream. Client controls request from its side but has nothing about data transfer as it is done by client. The only identification is that output stream is closed.