refs 2122

- GSNPositionedEditPartBase*: Avoid code duplication by pushing refreshDecorationFigure() to PositionedEditPartBase
- PositionedEditPartBase.refreshDecorationFigure()
  - Avoid SWT Image leak by reusing the same icons
  - Add more null-checks to implementation
- MarkerViewPart -> column updater: Avoid SWT Image leak by disposing old image before setting a new one

refs 2255

refs 2255

- 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 2055

refs 2055

refs 1491,2203

- Instead, ensure that DiagramEditorBase has the focus when a child edit part is added or removed
- This works around #2207 and also the same part of #1491 as with the old workaround
- Summing up:
   - Undo/redo of operations on the model only works if either the NavigatorViewPart or a DiagramEditorBase has the focus
   - This makes sense if the active view provides editable items itself (e.g., the GenericAnnotationView) *and* provides undo/redo (currently not the case for GenericAnnotationView).
   - For other (read-only) view (e.g., Model Markers), this behavior is confusing for the user
refs 2207,1491

refs 1491

refs 2159

refs 2067

refs 2093

refs 2093

refs 2093

refs 2093

refs 2093

refs 2093

refs 2093

refs 2093

refs 2093

refs 2093

refs 2093

refs 1493

refs 2030

refs 2061

refs 2061

refs 2028

refs 2048

refs 2011

refs 1960

No commit message

refs 1895