DAQAggregator for all setups about daqaggregator

Adding to point 4: hardcoded cdaq info
RelationMapper.getTopFMMForPartition contains hardcoded TTCP names "CPM-PRI" and "CPM-SEC" and hardcoded trigger name "TCDS-PRI"

[hsakulin]

1. ad CPM-PRI and CPM-SEC: this list should be extended to any partition starting with CPM, LPM, DVCPM, DVLPM (with case ignored).

2. Getting the trigger name:

from the new tcdsFM flashList you will get the pmURL, pmLID and pmService

Using pmURL and pmService you need to loop over all PMs in all triggers. If you find a match of a PM to the pmURL and pmService, you know what trigger you are using.

If there is no TCDSFM flash list available, try to find a Trigger with name GTPe. But in this case we need some special treatment to find the top level FMM as the GTPe has no PMs and iCIs and PIs. In this case the FMMTriggerLinks go directly from the top level FMM to the trigger. lpmNr and iciNr are -1, triggerIO gives the IO on the GTPe.

If you can work on getting the pmURL and pmService into this method, I can help with the rest of the code.

Implemented, without the special treatment when the GTPe trigger is selected due to lacking TCDSFM flashlist information.
You can review the code here: https://github.com/mvougiou/DAQAggregator/blob/dev/src/main/java/rcms/utilities/daqaggregator/mappers/RelationMapper.java#L384

If this is correct, we can proceed to the special case.