This is the implementation for the specification change done in a recent
commit.

- ControlSystemModule
- VirtualModule
- findTag
- excludeTag

and some related functions.

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

Implement systematic tests for exception handling along specification.

This fixes redmin issues #8374, #8520 and #8364.

This is changed behaviour introduced with c9948142

It was agreed to never do this. What strings are for display only and should not be analysed, neither by tests nor by applications.

- Also removed race conditions in the test.

Print test name.

- use DummyRegister::getRawAccessor for access to backend registers.
- read and write convenience methods for rawAccessor.

- runtimeErrorHandling_testPushTypeReadNonBlocking

- Reworked header.

- Reworked header.

- Reworked Header.
- Revised variable name. version -> versionBeforeRuntimeError

fixture_with_poll_and_push_input exposes pollVariable, pushVariable as
refernce types for convenience.

- Introduced PollModule::triggerRead
- status/message process variable are now instantiated in the fixture
- use name scheme for tests:
    runtimeErrorReporting
     - runtimeErrorReporting_faultReporting

The fixture in testExceptionHandling.cc created the ChimeraTK::TestFacility before the
ChimeraTK::Application. This is unspported.

The TestFacility implicity requries an Application instance already existing before being
initialized. Changing the oder of member declaration solved the exception being thrown from the
fixture.