Enhancement separate artemis into encapsulated sub-projects

Explore the ability to separate the core of the project from the various sub-project components:

A potential list of new repositories:

Artemis-analysis - top-level repository dependent on the core artemis project and various sub-projects depending on the analysis. This package may also include user-defined tools as required for a specific analysis and derive from the ToolBase class.
Artemis-formats - Collection of data models written in proto language
Artemis-tools - analytical tools used in artemis analysis. An advantage of the Artemis framework is that tools are retrieved via name, therefore algorithms in the framework do no have an explicit module dependency. The module import would appear in the analysis code.
Artemis-cpptools - (primarily) arrow-based tools written in c++ with python bindings. The artemis tool would wrap the bindings. This is a current bottleneck to the project, so would improve development by separating problems in building libraries.
Cronus - (previous project) metastore service, ideally can be used as a standalone tool for managing any data project.
Dolos - simulation framework, currently simutable in artemis

I'll explore these ideas a bit to see how this will work, setup some dev branches, repos and supporting documentation.

artemis-analytics / artemis