- Change return type of getValue() to T
 - This allows for more type safe implementation of the underlying calculations
 - The former abstract base class DerivedAnnotationBase used Object as a return type for getValue() to due an EMF code generation bug for generics if the base class is located in a different .ecore file than the concrete class. For interfaces, this bug is not triggered.
  
refs 1841

Introduce "derived" annotation, i.e. based on calculations instead of explicit annotations / model contents can be implemented

- DerivedAnnotationBase meta-model element, with getValue() EOperation, and a extensive documentation.
- Corresponding DerivedAnnotationValueProviderBase, implementing a read-only, text-view of the calculation result
- To implement the above, move handling of annotation EClass & factory to ValueProviderBase

refs 1841

refs 2093

refs 2093

refs 2093

refs 2093

refs 2049

refs 2028

refs 2048

refs 1868

refs 1868

updated the ecore & genmodel models to Kepler (files are strucutrally identical but textually different, hence Eclipse was always displaying local differences)
refs 1868

refs 1841

refs 1841

refs 1943

fix repeated coverage analysis error
add no id migration process
refs 1801

added new specification for memory and sil in scheduling model instead
moved addSpecifications functionality to tooling base
refs 1598

refs 1732

refs 1686

refs 1590

refs 1542

refs 1544

refs 1565

refs 1565

refs 1542

refs 1529

refs 1369

refs 1369

refs 1411

refs 1411

refs 1411

refs 1249

refs 1222

refs 1179