All IFFF sources must be consistently readable/writable. A logic error
is thrown if this is not the case.

* compiles but untested
* existing tests for app->CS still passing.

- Shows up in Doocs
- Test does not check functionality yet, just that it's there

- was confusing milliseconds and microseconds for the archiver
- was not setting the global time stamp

By default, the timestamp that is attached to a variable is the global time stamp, which is only set updated by update() in the adapter, which is not used otherwise.
The adapter already was setting it for the time stamp that is attached to the variable itself, but not for the time stamp that used for archiving. This has been fixed. Now the time stamps in the Doocs histories are set correctly.

To test it run example2 of ApplicationCore, togehter with the oven_sim simulation and watch Oven.heatingCurrent.HIST

output warning if data is thrown away due to failed consistency matching between macro pulse number and actual data

Workaround for the svr_writer thread (of DOOCS) to block location mutexes for a very long time if many big D_spectrum are written. The write is now only done if necessary (i.e. after a modification) and the lock is released for a short period of time to make sure RPC calls don't get blocked for too long.

Allow to set the data matching mode. This for now only allows to switch off the DataConsistencyGroup matching for the attached macro pulse number.

Fixes #28

Started implementing consistent macro pulse numbers in process variables. Only scalars at the moment.
No dediacted tests yet, but adapted ZMQ test which failed.

This commit belongs to issue #4, allow to set the EqFct code in mapping file.
In VariableMapper a std::map with location(string) and code(int) was added.
With getLocationAndCode() this map is returned and used in eq_creat.cc to add missing locations with
10 default, or with 'code' set in the <location> tag in the mappinmg xml file.

 - Introduce a new D_xy tag which takes x_source and y_source
 - The two sources are attached to a DataConsistentcyGroup. Only If the
   consistency group signalizes a consistent state, the data is updated

It basically decorated the AutoPropertyDescription with the type which
is now in AutpPropertyDescription

Parse "type" attribute for normal properties

Bubble up the type to the parent class