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

Improvement8453 drothe large array persistency

- 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

- add new elements
- add persist element
- make definition less dependent on ordering in XML file
Now, all but one test xmls validate, and the one exception should
actually not do so.

Previous attempt to work around the tine linking issue did not work.

This is a work around for not finding libtinemt at runtime. The DOOCS serverlib is lacking the RPATH, hence its dependencies are not found. If clientlib is linked first, tine is already linked.

Search explicitly for libgul14 which is required by DOOCS libraries

- EqCall::get() now returns comp_code, which can be -2, -1, 0 or 1.
  Before it was -1 (error) and 0 (ok).
  Only tests are accected. The library itself did not change.

- The macro is getting the name from the test suite, which is done with a #define. At this point the auto-formatter puts spaces in between because it thinks its a minus sign.

Test accomapnying the previous fix that if data on incoming variables is
sent out via ZMQ and data matching was none that there will be an event
id attached to it

Also, for the "trivial" datatypes such as scalar, array, IFFF enable
attaching a macropulse number on incoming variables so we can send out
updates from e.g. JDDD panels out via ZMQ

No test yet, hence ticket added on github #63

Reason: otherwise error messages are sometimes appearing at server start/shutdown because sending is not possible at that time.