ScriptedInitialisationHandler: catch boost exceptions and throw ChimeraTK logic_error with improved what() message

to check whether stepApplication() can execute...

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

This fixes redmine issue #8358 (#3 on github)

* spec tests: Data validity propagation
* update documentation links spec <-> tests

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

Implement systematic tests for exception handling along specification.

This fixes redmin issues #8374, #8520 and #8364.

This was a left-over from times when no proper initial value propagation
and exception handling was implemented in ApplicationCore. Waiting until
the backends are open is anyway not sufficient, since the DeviceModule
needs to finish the recovery procedure. If any test would still rely on
this (anti-)feature, it would be subject to race conditions.

The wait is removed because it prevents important tests for the
exception handling specification. In particular, tests which
intentionally break devices during startup of the application would not
be implementable.

When writing special modules (e.g. the MicroDAQ module) it may be necessary to both override and call this function explicitly.

add Application::dumpModuleConnectionGraph()