Revert "ExceptionHandlingDecorator: re-introduced while loop. Behaviour is now closer to previous one because it re-tries the read until it succeeds"

Looping the postAction makes no sense. The loop only worked for the transfer itself.

This reverts commit f7f35074.

ExceptionHandlingDecorator: re-introduced while loop. Behaviour is now closer to previous one because it re-tries the read until it succeeds

* doGenericPostAction is void
* removed endless loop in doGenericPostAction
* only wait for recovery if application is running in multi-threaded mode
* fixed return value for doReadTransferXxx in case transfer is not allowed

	TODO doGenericPostAction
	DONE all the rest

	does not compile, due to missing overrides

	-waitting for recovery is now outsourced in function
	DeviceModule::waitForRecovery()

	-everywhere where the function is called, the new function is now called.

Fixes #144

- The direction cannot be determined from the accessor which is being decorated
- Fixed wrong usage of feeding/consuming in Applicaton::createDeviceVariable. Was used consistently wrong, so there was no behaviour bug. But the code was confusing because the direction was wrong.

Tests still failing.

- All accessors come up in exception state.
- Read-accessors increase counter in init phase

Assertion is gone, but tests still failing

  - EntityOwner has individual counters for both events
  - Adapted all instances of increment/decrementDataFaultCounter
  - Not changed getDataValidity() implementation yet
  - Tests failing

- Exception handling decorator does not allow to leave testable mode before
  devices are up
- Test facility makes sure that testable mode counter is zero at the end of startApplication()

wip #47: register accessor for write after open in DeviceModule if write cannot be performed in initialisation phase

change declaration of 'decrementDataFaultCounter' in 'EntityOwner' to take a bool parameter and adjust rest of the code to it
implement 'decrementDataFaultCounter' in 'ApplicationModule' according to ticket #95 -> rewrite all outputs when 'faultCounter' goes from 1 to 0

remove commented part of ExceptionHandlingDecorator - 'void doPreRead() override' and its implementation

removed doPreRead() / doPreWrite() , doPostRead() / doPostWrite() from ExceptionHandlingDecorator - tests are now failing

  - Handle illegal writes to read-only accessors in doPreWrite().
    Otherwise, attempting to write to the recovery accessor would result
    in a nullpointer access.
  - Related test case.

  - Cleaned up comments
  - Place using-declaration of buffer_2D to class definition so the base
    class name can be omitted in the implementation

- remove "void ExceptionHandlingDecorator::setDataValidity(DataValidity newValidity)"
- add "void ExceptionHandlingDecorator::setOwner(EntityOwner* owner)" and remove owner setting in constructor

  - Cleanup:

    - Reorder code in Application::createDeviceVariable
    - Separated ExceptionHandlingDecorator constructors for writable and
      non-writable registers
    - cleaned up doPreWrite

- New flag parameter for ExceptionHandlingDecorator::genericTransfer.
  Method does not invalidate data if flag invalidateOnFailure is set to
  false.
- Write related methods in ExceptionHandlingDecorator set
  invalidateOnFailure flag to false

Changes resolve ticket #57.

  - First compiling version, tests pass, hope it works...
  - Needs some tweaking

- Exception handling decorator and ThreadedFanOut send condition variable notificatios via the DeviceModule
- FanOut sends terminate to impl and all slaves.
Solves (some?) shutdown issues, but breaks bi-directional array test.

Otherwise it is impossible to shut-down the server if the device could
not be opened at all or is in constant error state