Problem: tight coupling of basic messages, sync manager

this is refactoring issue,

current source can be divided into separate modules
also class depth are deep
need to make depth more shallow by moving to other module

it seems better to divide into reusable modules like this

1. cosmos,tendermit messages , events -> chain-data
these classes should be auto-generated to prevent human errors.
also javascript annotation is automatically done via protobuf level.

also these messages can be very huge, we may miss some of types manually, in that case,
in parsing json, there can be assertion errors

2. sync manager -> chain-sync
3. posgress related -> chain-indexing , and decouple database interface loose
projection codes

by this issue, workloads can be separated,
maintenance will be easier
also we can support other db , like oracle, mysql
even sqlite,mongodb