Signed-off-by: Alexander Diewald <diewald@fortiss.org>

refs 3177

TODO: Use progress monitor of Eclipse Job
refs 2898

refs 2602

refs 2458

- Annotations are now instantiated in ElementCompositorService. Hence, this migration will not be required in the future.
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

- Change view ID to "org.fortiss.tooling.base.ui.annotationView" and define a Java String constant for it
refs 2133,1841

- Prevent nested calls of selectionChanged() which could trigger a refresh of the table before all column label providers / editing support has been initialized
refs 1841

  - Move label provider to dedicated package
  - Move generic annotation view to dedicated package
  - Move inner classes of GenericAnnotationView to separate classes (filter support in dedicated package)
- Small documentation updates
- No functional change
refs 1841

- Introduce sub packages for annotation framework (see org.fortiss.tooling.base.ui.annotation -> package.html for documentation)
- Standardize class names

refs 1841

refs 1841

refs 1841

refs 311