Closes #379

We were holding an std::vector of an incomplete type
(VariableNetworkNode) in a struct (ProcessVariableProperties), which
is not allowed. This fix changes it into an std::vector of shared_ptrs.
Since we are exposing this vector via ProcessVariableProxy::getNodes(),
this presents a breaking API change. Since this is used mostly
internally, this should not break much.

Fixes #8357

Fixes #7879

This helps in two ways:
1. Doxygen is confused if there are multiple class defintions with the
   same name, which happens frequently in tests, e.g. "ModuleA"
2. Doxygen shows rather prominently all classes defined in the tests
   when viewing the Class List, while the important classes are "hidden"
   at first below the ChimeraTK namespace.

Dietrich Rothe authored 7 months ago and Dietrich Rothe committed 7 months ago

* most useful with StatusOutputs, where automatic propagation of
  'data invalid' status is often not wanted
* Change default behavior of StatusOutput and StatusWithMessage.
  By default, they no longer propagate DataValidity=invalid of owning module.
  They still propage DataValidity=invalid of explicitly set for the output.
* Adapt test of DataValidity propagation for StatusOutput
* Adapt test of StatusMonitor to new StatusOutput behaviour

Dietrich Rothe authored 7 months ago and Dietrich Rothe committed 7 months ago

"!sometag" is a negated tag which annihilates with "sometag"
negated tags can be added like normal tags, and are used to remove their counterparts

This is another instance of the race conditioon fixed a few days ago
(with eb81711e).

The racy behaviour is acceptable, so the test is modified to accept it.

StatusAggregator was aggregating downstream aggregators according to their
input tags instead of the output tags.

* fix: Ignore data validity through return channels

* chore: Minor linter fixes

* fix: Do not modify model while iterating in XML generator

* fix: Change XML generator for TriggerReceivers

Give it a chance to comply with the XSD we provide

* fix: Update XML output XSD for changed output

 - Add Void and Boolean
 - Add TriggerReciever
 - Make class optional

* chore: Update test for XML generator

Add a DeviceModule whose absence was causing the XML generator to fail unnoticed

If the StatusAggregator would propagate the DataValidity of its inputs
normally, device errors (runtime exceptions) will normally be presented
as an invalid because values from the device will be aggregated  often
with the same StatusAggregator (if it is on the top level of the app).
This is clearly undesired.

The StatusAggregator did not pass on messages unless the
StatusWithMessage was from another StatusAggregator. StatusWithMessage
outputs from normal modules were treated like normal StatusOutputs
without message.

BREAKING CHANGE:
Since previously more characters were allowed (with possibly adverse
effects), this commit may force application developers and/or system
integrators to take action by changing variable names such that they
comply to the rules. Only alphanumeric characters and the underscore
are allowed, while slashes (and dots) are understood as hierarchy
separators.

- fix EntityOwner::constant() violates character restrictions
- Utilities::stripName() was broken in multiple ways. It has been
  changed into a true, reversible escaping algorithm and subsequently
  renamed into Utilities::escapeName().
- Utilities::unescapeName() is introduced.

BREAKING CHANGE: This commit will break applications which either
- rely on the names of device status PVs for devices which contain
  illegal characters (e.g. when using a CDD directly instead of a
  dmap file alias), or
- use Utilities::stripName() directly.

* Disable deprecation warnings
* Fix linter findings
* fix: Compiler warnings regarding internal linkage
* fix: Mask memory leak

---------

Co-authored-by: Martin Hierholzer <martin.hierholzer@desy.de>