Server entities versioning

[hasan7n]

Editing entities (e.g. mlcubes) during operation might be needed (e.g. bug fix, additional metrics, ...). For this, a discussion was held about whether editing an entity will result in a totally new one, or a newer version of it.

Current discussion state:
Allow “editing” through versioning. Any new change creates a different version of the entity.
Provide tools for image-checking. Add policy validation
We need to keep the registration information from previous versions. How do we keep track of history? Have a common field (e.g. name) that can be queried to get all versions
How to deal with bug fixes and associations? Benchmark provides unit tests to automatically sign an implementation.

[hasan7n]

converted to an issue