- Add Id, version, and ConQAT tags to XML files

* Mainly documentation cleanup
* Remove some commented out code

org.fortiss.tooling.kernel.internal.storage.eclipse.ModelContext:
org.fortiss.tooling.kernel.utils.EMFResourceUtils:
 - Resolve B.19 issue (numbering scheme as of Aug. 14, <https://af3-developer.fortiss.org/projects/autofocus3/wiki/Check-list_for_Code_Reviews/56>) "Use static imports"
refs 2255

refs 2208

- Fix addition of spurious undo/redo command by ensuring that annotations are instantiated from HierarchicElementCompositorBase.compose()
- Derived compositors that override compose() must ensure that call their parent classes' implementation
refs 2208

- Move annotation value service, annotation value provider base classes and annotation extension point to org.foritss.tooling.base
- Remove createEditingSupport() from IAnnotationValueProviderBase and move functionality to org.fortiss.tooling.base.ui.annotation.editingsupport.EditingSupportFactory instead
- Rename extension point to org.fortiss.tooling.base.annotation.

Example binding:

<extension point="org.fortiss.tooling.base.annotation">
  <annotation binding="org.fortiss.af3.timing.annotation.valueprovider.CIValueProvider">
     <modelElementClass modelElementClass="org.fortiss.af3.component.model.Component"/>
  </annotation>
</extension
- Adapt all known users of annotation framework to new structure
- The change is a preparation to fix #2208, i.e. to put the instantiation of a model element and its annotations into a single undo/redo command
refs 2208

- Document that getAnnotation(IModelElement modelElement, Class<T> clazz) wraps the model access into a command
refs 2199,1841

- Ensure that that AnnotationsUtils.getAnnotation(IModelElement modelElement, Class<T> clazz)  actually wraps the extraction / creation of an annotation into a command
- DAGExtractionWithoutDeployment: use this variant
refs 2199,1841

- Adjust all annotations that inherited from IDerivedAnnotation to use the new DerivedAnnotationBase class
- EOperation cleanup
- Move getValue() from org.fortiss.tooling.base.utils.AnnotationUtils to org.fortiss.tooling.base.model.base.impl.DerivedAnnotationBaseStaticImpl

  - Add getAnnotation(IModelElement, Class<T> clazz, boolean)  variant that lets the caller control if the potential instantiation of an annotation should be wrapped into a command.
  - The original getAnnotation(IModelElement, Class<T> clazz) variant still exists and still defaults to wrapping the instantiation into a command
- AnalysisMigrationProvider / SafetySpecToAnnotationMigrationProvider: Use the new method to prevent the creation of a command in order to prevent the use of the IPersistencyService during the migration (workaround for the annotation-related aspect of #2010)
refs 2010,2172

- Remove redundant dependencies (i.e., those, that are already contained and re-exported by the actual dependencies)

- getAnnotation(): Wrap creation of new Annotation into command since this method might easily be called from a context that cannot directly manipulate the model (e.g., from the GUI context)
refs 2178

SafetyUtils.getParentSpecificationsWithType() --> AnnotationUtils.getParentAnnotationsWithType()

AnnotationUtils: Add TODO to remove workaround that should be no longer required after IDE dev tools update.
refs 2171

Add <T extends IAnnotatedSpecification> T getAnnotation(IModelElement modelElement, Class<T> clazz),

a method to safely obtain an annotation for a given modelElement (and to create it, if it does not exist yet).
refs 1841

Extends the Derived annotation, such that element-specfic values can be returned; Useful for aggregate annotations.
refs 2150

refs 2150

 - 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