allows to control whether to wait for device recoveries in stepApplication

This prevents stepApplication() to return too early (e.g. right after start) when the device is not yet initialised.

Note: is has been verified that there is no race condition at the beginning despite the counter is only incremented during the test (by introducing an artificial delay at the beginning of handleException()). It works, because testable mode waits until all devices are opened. In testable mode, this check is now equivalent to the devices being also initialised (when the testableModeLock is obtained and the counter is checked).

ScalarPollInput and ArrayPollInput: Removed doReadTransfer, which does not make sense in the interface

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

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

Replaces calls to doXxxTransferYyy of the TransferElement by the
corresponding xxxTransferYyy call

Remove DeviceModule::writeOnOpen

Fixes #144

Clarified details in spec_initialValuePropagation and fixed wrong reference in exceptionHandlingDesign

  - lower case commands
  - place test executables in top-level build directory