If a macro pulse number is attached to a property which is mapped to a
variable mapped to also other properties, the update from the other,
writeable property was not getting through due to the consistency check.
This check is now effectively disabled in that case, which is ok, since
the update is anyway uncorrelated to the macro pulse number (since
coming from e.g. the operator).

The location pointer can no longer be nullptr even when just using the
adapter part of the DoocsProcessScalar class.

If a writeable process variable is mapped to multiple properties, so far
the values in the properties were not synchronised, i.e. writing to one
property did not propagate the value to the other connected properties.
This synchronisation is now implemented.

Note that inconsistencies might occur when more than one of the
properties is writeable, hence a warning will be displayed in this case.

* 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>

Modifying the spectrum parameters causes our code to send out data for
the same MP with multiple timestamps, which confuses the DOOCS DAQ

* partial fix for #9836

This fixes that cleared error codes appear in DOOCS history where error
is not yet cleared.
It is only a partial fix since the history still contains more data than
was intended; intended was only first invalid data point

* remove comments about outdated concept

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

Identical time stamps are considered to have identical data when DOOCS checks for inconsistencies on silent ZeroMQ connections. If on the same property new data is set without changing the VersionNumber, the timestamp will now be altered by 1 microsecond.

This is more like a temporary work around. A feature request to DOOCS should be made to introduce a distinction between a "server timestamp" and a "source timestamp" like it is realised in OPC UA.

Also a potential better solution to the other part of the problem inside ApplicationCore is described here: https://redmine.msktools.desy.de/issues/9723 

fix headers not being shown in QtCreator

Wip/bool and void

Consolidate coverage options

 - Remove Makefile.coverage.in
 - Drop BUILD_COVERAGE_ON_DEBUG for ENABLE_COVERAGE_REPORT (defaults to
    on if included)
 - Add clean-gcda target

this is required for dcmctrl7 config

This will be used unless overriden in doocs server conf

This fixes issues when using LaTeX in doxygen

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