Update lisk-chain to use encoded data to store

[shuse2]

Description

Update lisk-chain to receive decoded value based on new schema, and store encoded value.

• Rename BlockInstance schema to Block, and update to the new schema defined in the LIP
• Remove BlockJSON and similar types
• Create block_adaptor to register asset schema per version
• Rename serialze/deserialize to encode/decode
• Update to store encoded value in storage and data access
• Update lisk-chain to receive registeredBlockHeaders and accountAsset schema, and all account and block header should accept generic for the asset.
• Update account state store to accept key as buffer
• Update Account class to use the definition https://github.com/LiskHQ/lips/blob/master/proposals/lip-0030.md
• Update block header to use the definition https://github.com/LiskHQ/lips/blob/master/proposals/lip-0029.md
• Update lisk-cryptography usage in the framework

Motivation

In order to reduce the storage size, and consistently use the encoded value, chain should store the encoded data.

Acceptance Criteria

• All tests are updated
• Update all affected area using the block type
• All unnecessary types are removed
• Chain should not know the content of asset

Additional Information

Related LIP: https://github.com/LiskHQ/lips/blob/master/proposals/lip-0029.md

Related issues: #5200 #5238