- Fix default setting for imported locations (solves #39)
  - Test for imported scalar properties

Since Doocs 20.1 this is thrown if the name of the property exceeds 64
characters

This is a new requirement from ApplicationCore.

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

This reverts commit aa0bd46e.

It does not fix the bug.

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.

 - Preallocate the unordered set with worst-case size before the loop
 - Perform insert and lock in one step using the return value of insert

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

Do not throw exception if the eq_fct_code in the DOOCS config file is not 10 and no code has expilicitly specified in the DoocsVariableMap.xml file.

throw error if a read-only spectrum is defined with more than one buffer

Fixes #28

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