Remove O(m) DB queries

When querying UTXOs using Asset type, aggregating UTXOs by account, and creating a snapshot, the Indexer scans all the UTXOs that have a specific account or a specific asset type.

When a user opens a CodeChain web wallet, wallet requests the total amount of assets that the user has to the Indexer. Indexer sends a query that scans all the UTXOs that the user has. If the number of UTXOs that the user has is `m`, the upper bound of the query is `O(m)`.

### How to solve

Make APIs return sub results that read k rows in the DB. The Web wallet or Hub should request the maximum `[n/k]` number of API calls to get all the results. The upper bound of each query is O(k*log m). Then there won't be a single slow query that consumes all the resources(CPU, Memory, disk I/O) in the DB.

首先定位用于 Asset-type UTXO 查询、账户聚合、快照创建以及 web wallet 或 Hub 使用的 API 的 Indexer 入口点。检查这些查询当前如何扫描结果，并确定 API 和 consumer 需要进行哪些更改，以便分批获取结果且每批有明确上限；完成的标准是没有任何单个请求扫描全部 m 个 UTXO。

由索引模型根据 Issue 内容生成。