- UniqueIdUtils:
    - Remove fixMissingIDs(final ITopLevelElement modelElement)
      (only used in one place)
    - fixMissingIDs(EObject object, EObject existingModel): Do not wrap
      model modification into a command. This is up to the caller of
      this method (e.g., the command stack is not available in tests) 
- Remove IDMigrationProvider: Fixup of missing / duplicated is handled
  in ModelContext
- ModelContext: Use nonDirtyingCommand, and automatically save model
  in case IDs have been fixed

Issue-Ref: 3369
Signed-off-by: Simon Barner <barner@fortiss.org>

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

refs 3177

refs 3192

refs 3026

refs 2489

- Add and register {@link RemoveDuplicatedAnnotationsMigrationProvider} that removes duplicated {@link IAnnotatedSpecification}s from a model. These have been observed for a couple of models and might indicate an internal problem.

- 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

refs 1868

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