feat: big genesis file

[dudong2]

Description

As the genesis.json file based migration progressed, the function to write and load large files to the db was required. The block size of leveldb is limited to 4gb. Therefore, if the genesis.json file exceeds 4gb, a way to divide and save it is needed.

• It divide the genesis data into 100MB units and save them in the db as keys genesisDoc0, genesisDoc1, ... genesisDoc255 (here int means byte). When divided into larger units (1GB, ...), the test could not be successed due to ci error, so the size was set at 100MB. Also, since 100MB * 255 = 25.5GB in this case, I figured it would be fine in most cases.

Closes: #577

[codecov[bot]]

Codecov Report

Merging #576 (5af9711) into main (7fcbb0f) will increase coverage by 0.19%. The diff coverage is 68.00%.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## main #576 +/- ## ========================================== + Coverage 66.19% 66.39% +0.19% ========================================== Files 277 278 +1 Lines 36946 37052 +106 ========================================== + Hits 24456 24599 +143 + Misses 10733 10682 -51 - Partials 1757 1771 +14 ``` | [Impacted Files](https://codecov.io/gh/line/ostracon/pull/576?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=line) | Coverage Δ | | |---|---|---| | [node/node.go](https://codecov.io/gh/line/ostracon/pull/576?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=line#diff-bm9kZS9ub2RlLmdv) | `61.10% <68.00%> (+0.50%)` | :arrow_up: | ... and [17 files with indirect coverage changes](https://codecov.io/gh/line/ostracon/pull/576/indirect-changes?src=pr&el=tree-more&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=line)

[torao]

The e2e tests seem to fail all the time. E2e tests often have non-reproducible errors related to asynchronous processing, but this happens a lot, maybe there is still some code that has not been fixed enough.

Looking at the error log, it seems that SIGSEGV is happening on validator04 out of the four validators. https://github.com/line/ostracon/actions/runs/4363272772/jobs/7670216595#step:10:360

Is there anything we can do to help?