- Have to use float because it that's what is descibed in the map file.
  We are skipping the lmap which would adapt firmware types to the application type, so the type has to match
  The type has changed because it was always wrongly set to double for all floating types data, although the catalogue suggests float. This fix requires the test to be adapted.

- testCircularDependencyFaultyFlags now uses modern AC without defining CS module and overriding defineConnections()

# Please enter the commit message for your changes. Lines starting
# with '#' will be ignored, and an empty message aborts the commit.
#
# On branch master
# Your branch is up to date with 'origin/master'.
#
# Changes to be committed:
#	modified:   include/DeviceModule.h
#	modified:   src/DeviceModule.cc
#	modified:   tests/executables_src/testCircularDependencyFaultyFlags.cc
#
# Untracked files:
#	build-example-Desktop-Debug/
#	build-example2-Desktop-Debug/
#	build-example_status_monitor-Desktop-Debug/
#	demoBidirectionalVariables/
#	example2b/
#	include/ApplicationModule_BACKUP_1938963.h
#	include/ApplicationModule_BASE_1938963.h
#	include/ApplicationModule_LOCAL_1938963.h
#	include/ApplicationModule_REMOTE_1938963.h
#	message.txt
#	tests/testVirtualHierarchy.xlmap
#

The new order has the following advantages:
- values 0=OK and 1=Fault are compatible with frequent use of booleans like "is_error"
- values are matching ("accidentally") the DOOCS convention

modernise StatusMonitor interface

add convenient way to create constant PVs for use in generic modules

Killenb/7834 circular dependency faulty flags

Circular dependency detection: Outputs which are pogrammatically set to faulty are treated like external inputs.

Wip mhier 7982 status aggregator

After discussion with Martin K. we concluded that this monitor makes no sense. Legit cases should use the ExactMonitor
instead (if e.g. a boolean on/off configuration switch is to be observed). The monitoring of a Status value makes
no sense, since we would then have a monitor monitoring another monitor. In that case, the behaviour of the other
monitor should either be corrected, or the monitors should be aggregated with the right aggregator mode.

- introduce StatusOutput class
- rename ChimeraTK::States enum to ChimeraTK::StatusOutput::Status and make strongly-typed
- introduce reserved tags to detect StatusOutputs to be aggregated

- Implemented but not tested yet
- All existing tests passing