HCS running hash should concatenate message hash & not message

[tinker-michaelj]

Summary of the defect
The new topicRunningHash of a topic receiving a ConsensusSubmitMessage should be the SHA-384 digest of, in order:

1. The previous topicRunningHash of the topic (48 bytes)
2. The topicRunningHashVersion (8 bytes)
3. The topic's shard (8 bytes)
4. The topic's realm (8 bytes)
5. The topic's number (8 bytes)
6. The number of seconds since the epoch before the ConsensusSubmitMessage reached consensus (8 bytes)
7. The number of nanoseconds since 6. before the ConsensusSubmitMessage reached consensus (4 bytes)
8. The topicSequenceNumber (8 bytes)
9. The output of the SHA-384 digest of the message bytes from the ConsensusSubmitMessage (48 bytes)
   But in fact, we have not versioned the topic running hash; and are updating the digest with the bytes of the submitted message, not their SHA-384 hash.

Suggested resolution

• Add a topicRunningHashVersion to the protobuf TransactionReceipt type.
• Correct the hash calculation.

Impact
Mirror nodes should store for each message, the version number of the record for it. That way, when checking the running hash, they know how to calculate it for both old messages and new messages.