Require e.g. when needing to report an exception programmatically

The previous implementation using the mutex had two issues:

1. The mutex was locked in a different thread than unlocked (DeviceModule constructor vs. handleException() thread). This results in undefined behaviour.
2. The boost::shared_mutex::lock_shared() function is not an interruption point, so applications did not terminate while waiting for initial values. (boost::latch::wait() is an interruption point.)

- testCircularDependencyFaultyFlags now uses modern AC without defining CS module and overriding defineConnections()

# Please enter the commit message for your changes. Lines starting
# with '#' will be ignored, and an empty message aborts the commit.
#
# On branch master
# Your branch is up to date with 'origin/master'.
#
# Changes to be committed:
#	modified:   include/DeviceModule.h
#	modified:   src/DeviceModule.cc
#	modified:   tests/executables_src/testCircularDependencyFaultyFlags.cc
#
# Untracked files:
#	build-example-Desktop-Debug/
#	build-example2-Desktop-Debug/
#	build-example_status_monitor-Desktop-Debug/
#	demoBidirectionalVariables/
#	example2b/
#	include/ApplicationModule_BACKUP_1938963.h
#	include/ApplicationModule_BASE_1938963.h
#	include/ApplicationModule_LOCAL_1938963.h
#	include/ApplicationModule_REMOTE_1938963.h
#	message.txt
#	tests/testVirtualHierarchy.xlmap
#

- Implemented but not tested yet
- All existing tests passing

- removed ExceptionHandlingDecorator::setOwnerValidity()

- removed DeviceModule::waitForRecovery()
- ExceptionHandlingDecorator is throwing to skip transfers

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)