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

 - AllocationTable.getAllocationTableCollection()
 - AllocationTableCollection.getAllocationTable(Class<T> allocationTableType)
refs 3343

 - Used to semantically mark AllocationTables and AllocationEntries (e.g., which layers of the system are connected by allocation, and which system entities)
 - Add IAllocationService.addAllocationEntryType() and getAllocationEntryTypes() to register and query IAllocationTypes
 - Apply IAllocationTypes specializations to Task, Partition and Hardware architecture allocations

2) Move TaskToExecutionUnitAllocationTable and TaskWcetTable to af3.task (to avoid circular dependencies that would arise from the introduction of IAllocationType)

3) Schedule model UI
 - Use IAllocationTypes to provide unified generic UI in af3.schedule.ui
 - Remove most of the temporary hacks since allocation[.ui] is now in the build
 - TODO: Remove SystemScheduleDeploymentPropertySection once Deployment has fully been replaced by AllocationTable

refs 2950,3188,3067

- As soon as a ParameterEntry is created, it can be annotated with a parameter that is related to the respective (source,target) element pair.
refs 2950

- Clear allocations when switching the source/target view. Ask for confirmation if the current set of allocation entries is not empty
refs 2950

- getSourceElements(type)
- getTargetElements(type)
refs 2950

refs 3192,3177

refs 2591

Adjust eOperations of AllocationTable to handle both IUnidirectional and IBidirectional allocations.
refs 2950

- bidirectional, i.e. if the source(s) can be determined from the target
- unidirectional, i.e., if multiple source(s) reference the same target(s)

It is mandatory that any concrete AllocationEntrys inherit either IBidirectional or IUnidirectional.

TODO: Correctly handle IUnidirectional allocation entries in the getSource/TargetElement[s] eOperations of AllocationTable
refs 2950

TODO
 - Filter fake top-level elements (e.g., component architecture)
 - Update view on model change
 - Reflect model hierarchy (e.g., tree for rows, ?? for columns) to disambiguate duplicated names
 - More cleanup
refs 2950

- Add getAllocationEntries(? extends AllocationEntry)

refs 2950

 o Allocation -> AllocationTable
 o Allocation.source/target -> Allocation.source/targetView
 o AllocationTable -> AllocationTableCollection
 o AllocationEntry.source/target -> AllocationEntiry.source/targetElement
- AllocationTable: add eOperations
 o getSourceElement(EList<IModelElement> targetElements)
 o getTargetElement(EList<IModelElement> sourceElements)
- AllocationTableStaticImpl
 o Add missing implementations
refs 2950

- Allocation
  - abstract
  - Add source and target model reference
refs 2950

refs 2950

refs 2950