DMS 0.5.x architecture

Key Points

DMS refactoring has two goals:

1. enable hybrid model, ip over lib-p2p integration, etc. and cross-platform integrations
2. implement cleaner architecture for efficiency and scalability;
3. as defined better in the milestone goal description #182 (closed)

Work Package Deliverables

No	Deliverable	Proof
1	NuNet computational model is chosen on conceptual level considering the challenges and issues encountered so far in development (including job orchestration and deployment semantics, data persistence, logging, error propagation, etc.)	Computational model is agreed upon, properly defined and documented in Whitepaper 3.0
2	The new DMS architecture is properly defined and described	architecture complies to the NuNet computation model descriptions; implementation work packages and issues can be opened and described based on the architecture description;

Timeline

Additional notes and context

1. See documents in folder https://drive.google.com/drive/folders/1Sx4aDoBbiU4tUZRhxeHrSdkfcTv-TEli?usp=drive_link, including:
2. Architecture / packages diagram by @dagimsisay , based on which the milestone was designed https://app.diagrams.net/#G18EBeCfM-WTT301KOeo1CU9A6aB7Zdx38#%7B%22pageId%22%3A%22YQ2wF7bl5_D1ox1odwqX%22%7D