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

Removed obsolete localValidity.

It is now inferred from the TransferType in doPostRead of the
MetaDataPropagatingRegisterAccessor, if the owning module's
version number gets updated.

Fixes #151

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

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

rename VersionNumberUpdatingRegisterDecorator into MetaDataPropagatingRegisterDecorator, as it does more than just updating the VersionNumber now

bidirectional variables: pass on version numbers in modules from the last blocking read on to any write operations, to resolve conflicts of concurrent variable updates properly