CU "golden" setpoint
Description
It would be necessary to have "golden setpoint" feature, that is something very similar to a setpoint/snapshot command and to an attribute default. This feature allows to save a limited number of setpoints identified by a tag that are bounded to a particular instance of a CU. These setpoints should be loaded into the CU at "_defineActionAndDataset" like others default attributes. The CU that have this setpoints loaded, should check periodically (in the default command or every cycle or after every command) if the output/input CU dataset matches one of this setpoints and return in a new system key the corresponding tag. So if the "setpoint" containts both input/output reference dataset means that the comparison should satisfy both (it must be possible to associate also a delta error in the "golden setpoint"), if just one of these is specified the comparison should be done just on the given one (input: compares just input setpoints, output: compares just output within a delta error). Of course these "golden setpoint" should work also as restore points with a snapshot restore command.
" (Include problem, use cases, benefits, and/or goals)