* Create test case for testing multiple modules having the same.

* Use message IDs to support modules with similar names.

ToDo: Remove variable connections to CS like with MicroDAQ.

* Use automatic connection via CS. Rebuild hierarchy in Logging module.

* Put logging variables into a separate hierarchy level.

* Let user write to alias via CS. Keep last message in the PV.

Before the message was always cleared after writing it. Now a new log
level is used to indicate the situation that write was called on the
message PV without calling sendMessage - it happens if the owning module
calls writeAll(). Now the last message of each sender is availble in the
CS.

* Add test with modified hierarchy.

* Clang formaat applied.

* Hide internal PVs. Use different internal tag to work with regex.

Introduce StatusWithMessage and StatusWithMessageReader which handle this.
It is used in DeviceModule error reporting.
This is a preparation in order that we can report errors consistently to DOOCS, in DoocsAdapter

make StatusAggregator use StatusWithMessage

it should output always status code + string
on the input side, connects to either status or status + string
corresponding string input is found automatically
NOTE: DeviceModule API change, the status output variables are
renamed from (status, message) to (status, status_message)!

update testing of DeviceModule outputs

because of API change of DeviceModule  (renamed message ->
status_message)

fix crash and improve message and test

- fix crash due to incorrect handling of cast to Derived
- improve message output
- make existing tests pass
- add test for status message of StatusAggregator

move StatusWithMessageReaderBase and Status def to ControlSystemAdapter

since it is required from ApplicationCore as well as from the adapters

Co-authored-by: d-rothe <39566710+d-rothe@users.noreply.github.com>

* optimization for StatusAggregator
make getPriority faster by making prio map static and reduce evaluation frequency

* get rid of compiler warning

* comment for statusPrio

Co-authored-by: Dietrich Rothe <dietrich.rothe@desy.de>

ScriptedInitialisationHandler: catch boost exceptions and throw ChimeraTK logic_error with improved what() message

The message of this exception is usually lost and the user is left with
an obscure error about not calling shutdown() in the constructor without
any clue what was wrong with the config

The new order has the following advantages:
- values 0=OK and 1=Fault are compatible with frequent use of booleans like "is_error"
- values are matching ("accidentally") the DOOCS convention

- introduce StatusOutput class
- rename ChimeraTK::States enum to ChimeraTK::StatusOutput::Status and make strongly-typed
- introduce reserved tags to detect StatusOutputs to be aggregated

Before it had to be stripped for all use cases anyway, so it is better to leave it out from the beginning.

* Fix initial msg. Add automatic connection to the LoggingModule.

Now the Logger is a VariableGroup and in the prepare() method an empty
msg is written once. This makes sure the LoggingModule is not waiting
for initial values of Loggers and messages by other Loggers get lost.

* Add message in case on modules with Logger are found.

* Fix test and remove implementation of removed method.

* Do not use hard coded tags but use default tags.

Now all tags given to the LoggingModule are used to look for senders.

The user can now also choose to publish messages only to the control
system.

Refactored.

Reading was done only in deeper levels inside the VariableGroups.

See 1af92147. Input accessors are now properly part of the ReadAny group which improves the deterministic behaviour.

This provides a strict guarantee for the order of updates w.r.t. trigger, especially for tests.