[Implement] MessagePack serialization; fixes #43

[samatstariongroup]

Prerequisites

• I have written a descriptive pull-request title
• I have verified that there are no overlapping pull-requests open
• I have verified that I am following the SysML2.NET code style guidelines
• I have provided test coverage for my change (where applicable)

Description

• Implemented a CDP4-COMET inspired MessagePack serialization library.
• Ignored reading.writing derived and redefined properties
• Payload class has predictable positions for objects and properties (required for MessagePack), where the various Core types are ordered by UML class name (not the whole namespace, let me know if you think the order is fine like this or whether we should sort on whole namespace)

Currently testing is done by reading in a JSON doc, serialize MessagePack to serialize to stream and deserialize. Once comparers as requested in issue #60 are available, tests need to be improved to verify equality of objects between json read and messagepack write -> read

[sonarqubecloud]

Quality Gate failed

Failed conditions
71.9% Coverage on New Code (required ≥ 80%)
C Reliability Rating on New Code (required ≥ A)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE