Now the writing in the DeviceModule is working.

Fixes #159

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

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

Fixes #144

- 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

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

	Ticket #79
	- documentation for addRecoveryAccessor() and getRecoverySharedMutex()

  - add list with shared ptr of transferElements for recovery write
  - add shared mutex

- ConfigReader is in ApplicationCore.h, but was including ApplicationCore.h itself
- Added include guards to ApplicationCore.h, although it's not stricktly needed (all included headers have one). Might speed up complilation because it makes it easier for the parser.

This is needed to add all device variables to e.g. the history module.

  (first part of #65)

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

supposedly fixed implementation, but tests are conceptually broken and/or implementation cannot be terminated

first implementation of device initialisation handler. Simple test passes, but needs to be extended.

implemented first interface change in DeviceModule to support initialisationHandlers. Test in place but failing due to missing implementation.

moved exception handling documentation into its own dox file and added documentation about DataValidity flag propagation

changed: device is not intialized in constructor anymore.

Test still does not work.
-Unable to get the exception status for the device throwing exception.
-Second device only works it has it's own trigger.