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 reverts commit bc329233.

We propagate the version to the module on any read, if it is on an
accessor with wait_for_new_data and there is new data (for
readNonBlocking/readLatest)

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

- recoveryLock now protects the whole critical section
- activateAsyncRead() is called on the device

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.

Lock is only released for accessors with wait_for_new_data on blocking
reads. This fixes usage of readLatest() in testable mode.

Set specification version to V1.0RC1

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

  - Added requirement that receivers are faulty on construction (1.8)
  - Clarified that validity can be set by the user code in 2.1.5

remove changes for debugging in test case testDirectConnectOpen

For receiving variables, the validity should be faulty after
construction, see data validity propagation spec 2.6.1.

restored write functionality of MetaDataPropagatingRegisterDecorator in case of locally set faulty status (DataValiditySpec 2.1.5)