Decouple payload encoder and add CBOR as an encoding mechanism

[namtruong]

This PR adds another type of payload encoding (CBOR) as the preferred codec with the view of replacing the legacy binary encoding mechanism. This is to make the EncodedPayload more extensible and also an enabler to accommodate any interoperability requirements in the future. Changes include

• Introduce EncodedPayloadCodec and store in an extra database column. Purpose of this is to maintain backward compatibility.
• Add EntityListeners that handle data encoding/decoding from/to database
• Heavy refactoring to decouple the payload encoder and perform lookup to work out the relevant encoder to use based on codec
• Mapping of api versions and preferred codec - publisher to encode and publish payload in preferred format depending on supportedApiVersions of the remote node
• Add CBOREncoder
• Refactoring unit tests

For now the scope of the change is for pushing payload between Tessera peer-to-peer

Part of the change was initially done in PR #1335 by @melowe

[Krish1979]

LGTM