View DTO structure

We found View/OverView DTOs to be rather ambiguous in meaning. To fix this we decided to refactor all View classes (causing a minor version bump to 1.1.0).

The following is our proposal:

1. View DTOs for just static information, so no relations These, we can call Summaries

   Naming scheme: [Entity][Purpose?]SummaryDTO Leave out purpose if you use all static information (including ID)

2. View DTOs with non-static information, these will come in multiple forms most likely These should extend from Summary DTOs

   These can use other View DTOs from other entities

   Naming scheme: [Entity][Purpose?]DetailsDTO Leave out purpose for those Views that include all information