[client-v2] Resource release

## 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.

まず client-v2 の queryRecords フローと Records の close ライフサイクルを追跡します。次に ConnectionRequestTimeoutException と Insert/Command の操作パスを調べ、リソース解放の動作を確認します。要求された孤立レスポンスのガードレール、プール枯渇の診断、タイムリーなリソース解放が定義され、テストでカバーされていれば完了です。

索引モデルが issue の本文から書いたものです。