Write tests for initial value initial value specification D.8

- tests still failing
- modifications incomplete
- cleanup needed

testProcessVariableRecovery: waiting for device to be opened avoids race conditin with runtime error

fixture_with_poll_and_push_input exposes pollVariable, pushVariable as
refernce types for convenience.

PollModule and PushModule now uses a void type promise to signal
mainLoop entry. The fixture class uses this to synchronize itself before
handling over control to the testcase code.

This way we do not have to depend on the test facility for this purpose.

Fixture with poll and push inputs can be reused in testing Exception handling.

Only the blocking read in wfnd TEs will update the module's version

This fixes a race condition when the initial value reading was not done
when the test started, creating unexpected version changes

- 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.

- Replaced all of them with normal DUMMY_WRITEABLE registers.

- fixed that ConsumingFanOut is propagating the data to the slaves in case of exceptions
- /testPropagateDataFaultFlag currently passing (still commented sections)

remove changes for debugging in test case testDirectConnectOpen