Update state store interface to support new information

[shuse2]

Description

• Update name of chainState to be consensusState, and this should not be exposed to the transaction.
• Update chainState to have lastBlockHeader when creating state store so that transaction can reference
• Update 'consensusStateto havelastBlockHeaders` which contains last 309 blocks when creating state store, which DPoS and BFT can reference.
• Update database name chain_state to consensus_state
• Update state store interface on lisk-transactions

interface StateStore {
    account: {
        get: (address: string) => Promise<Account>;
        getOrDefault: (address: string) => Promise<Account>;
        set: (address: string, value: Account) => void;
        finalize: (batch: any) => Promise<void>,
    },
    chain: {
        lastBlockHeader: BlockHeader;
        networkIdentifier: string;
    },
    consensus: {
        lastBlockHeaders: ReadonlyArray<BlockHeader>;
        get: <T>(key: string) => Promise<T>;
        set: <T>(key: string, value: T) => void;
        finalize: (batch: any) => Promise<void>,
    },
    finalize: () => Promise<void>, // take diff of all set and delete
}

Motivation

In order to support new type of transactions, state store needs to be updated.

Acceptance Criteria

• lisk-transactions should not include the interface for consensus state. Only chainState and accountState.
• Test that state store always includes lastBlockHeader, networkIdentifier and lastBlockHeaders on creation

Related Issues

#4915