Refactor data insertion logic

[iuwqyir]

TL;DR

Refactored data insertion process to allow the storage decide how to handle batched data.
E.g sql databases can use transactions and concurrency whereas memory storage can do everything sequentially

What changed?

• Introduced a new InsertDataForBlocks method in the IMainStorage interface.
• Removed individual insert methods for blocks, transactions, logs, and traces from the interface.
• Implemented InsertDataForBlocks in both ClickHouseConnector and MemoryConnector.
• Updated the Committer to use the new InsertDataForBlocks method instead of saveDataToMainStorage.
• Renamed insert methods in ClickHouseConnector and MemoryConnector to be private.

[iuwqyir]

• Test setup and reorg handling tests #95
• Refactor RPC client to use interface #94
• Add reorg handler functionality and configuration options #91
• Create storage functions for handling reorgs #90
• Refactor data insertion logic  #89 👈
• Refactor rpc for easier reuse #88
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @iuwqyir and the rest of your teammates on Graphite

[iuwqyir]

Merge activity

• Oct 10, 10:01 AM EDT: A user started a stack merge that includes this pull request via Graphite.
• Oct 10, 10:03 AM EDT: Graphite rebased this pull request as part of a merge.
• Oct 10, 10:04 AM EDT: A user merged this pull request with Graphite.