This is mandatory according to the documentation, otherwise we have 0
all the time and lose persisted data

BREAKING CHANGE: The new interface no longer allows to create the same type of
location with arbitrary location codes, hence we have to decide for a fixed
code now. Using a location code which is not 10 (as used by default) now
results in an exception.

* refactoring

- get rid of much of the code duplicates by moving functionality to base
class PropertyBase
- make timestamp handling more consistent
- make data consistency group usage more consistent accross different classes
- formal code style fixes
- some formal code cleaning and documentation

* copyright headers

* apply clang-format-14 -i <files>
* fix include order where messed up by autoformat

* docu for D_xy
* enable ZMQ for D_xy

* reduce number of linter warnings

* PropertyBase as seperate file

* put error into ZMQ status

Co-authored-by: Dietrich Rothe <dietrich.rothe@desy.de>
Co-authored-by: Martin Hierholzer <martin.hierholzer@desy.de>

* concept for error reporting to set_error
- destination is DOOCS EqFct::set_error(code, message)
- StatusMonitor variables and/or Device status variables as input
- configuration per location via xml
- only single data source for set_error
- consistent updates of error code and error message, to remove
duplicate log lines
this depends on changes in ApplicationCore/DeviceModule!
* remove deprecated use of boost/test/test_case_template.hpp
* make configuration of status message input unneccesary
it will be found from the naming convention
* some refactoring
which was neccesary because Status definitions moved to
ControlSystemAdapter
* add docu for set_error
* add basic test for set_error tag

Co-authored-by: Dietrich Rothe <dietrich.rothe@desy.de>

This can potentially be a severe performance issue, if an application has many persisted large arrays.

- arrays are now by default saved just like spectra
- Short arrays go into main server config file, long into separate files
- only if array is writable
- behaviour is configurable in order to return to default behaviour of
DOOCS

so far, only scalars work and the meta data (macro pulse number etc. is missing)

Removed update functions completely. The long sleep made the server unresponsive. Instead the call to run update in the tests was replaces with a sleep. Sometimes fails, as expected with a fixed timeout, but it was as hack anyway.

changed updater to run in its own thread. Tests still using doocs update, which is just doing an insanely long sleep of 1 second.

all EqFcts are using common updater. Tests passing, but locking is not done properly across EqFcts (race conditions with RPC calls possible).

git-svn-id: https://svnsrv.desy.de/desy/mtca4u_applications/DOOCS_Adapter/trunk@141 688d77b5-b833-4f6b-b27f-eb88d88625d6

removed useless 'dname' from constructor and hard-coded it. Introduced the real fctname for testing instead.

git-svn-id: https://svnsrv.desy.de/desy/mtca4u_applications/DOOCS_Adapter/trunk@135 688d77b5-b833-4f6b-b27f-eb88d88625d6

moved registering of doocs variables and containing the variables into the EqFct, so you can have multiple EqFcts per PVManager

git-svn-id: https://svnsrv.desy.de/desy/mtca4u_applications/DOOCS_Adapter/trunk@132 688d77b5-b833-4f6b-b27f-eb88d88625d6

git-svn-id: https://svnsrv.desy.de/desy/mtca4u_applications/DOOCS_Adapter/trunk@130 688d77b5-b833-4f6b-b27f-eb88d88625d6