Metadata for landscapes

[Alexander-Krause-Glau]

With each landscape we should persist a (to-be created) metamodel. In my current idea this new model is only a single POJO with some attributes. These attributes essentially summarize some information about the related landscape.

This approach might be necessary for a frontend replay mode of imported landscapes, since the user might need to filter imported lanscapes.

Additionally, this can be used in the dashboard-extension.

Potential attribute candidates are:

• timestampValue
• activityValue
• customName (users can change this property for easy recognition of desired landscapes, e.g., experiment-56)
• number of entity X (where x is systems, nodegroups, nodes, etc.)
• more?

Things to check:

• New service or endpoints in history-service?
• Related to Refactor Landscape-Service #107