Introduced SocketDetectorToDaqConnection

[denizergonul]

20.03 Updates:

CRTReader is not a DataReader. It's not an interface to read DAQ frames from a front-end (like DPDKReader) and send them to data handlers. Instead, it builds DAQ frames from raw electronics output. It's similar to Hermes FW, a functional block that prepares data and passes it on.
The new name, CRTFrameBuilder, eliminates confusion with standard DataReader modules and accurately reflects its role as a builder of DAQ frames rather than a reader.

CRT frame builders communicate with SocketWriter via IOM.

Note that the example session uses Bern configuration. We currently don't have a suitable emulator for this new module type.

---

Prior to this development, socket connection info resided in reader and writer configurations. Now, there is SocketDetectorToDaqConnection which has SocketDataSenders and SocketReceiver; SocketDataSender has the info socket type (TCP/UDP), local port and remote port; plus we make use of their NetworkInterface.ip_address to interpret them as local IP and remote IP.

CRT readers communicate with socket writers via IOM.
Socket readers communicate with DHLs via callbacks.

To try out:
drunc-unified-shell ssh-standalone config/daqsystemtest/example-configs.data.xml local-socket-1x1-config ${USER}-local-test

---

appmodel PR dte/crt_topology_change
daqsystemtest PR dte/crt_topology_change
crtmodules PR dte/crt_topology_change
asiolibs PR dte/crt_topology_change
daqconf PR dte/crt_cb_update
datahandlinglibs PR dte/cb_acquire
fdreadoutmodules PR dte/crt_rates

---

Type of change

• New feature or enhancement (non-breaking change which adds functionality)

[alessandrothea]

LGTM

[bieryAtFnal]

Closing this PR since the branch has been merged to the prep-release/fddaq-v5.6.0 branch in a different PR.