End users typically do not care that a particular action did NOT
trigger at a particular time and these messages will typically
reduce the utility of the CASE.PRT file. On important field cases
we've seen more than 100,000 such messages in a single run which is
quite overwhelming.
Since we're now directing the messages to the .DBG file instead
we're not taking away any diagnostic ability, merely altering the
location of the information.
Use libfmt's ability for format 'std::tm' objects to output
unambiguous dates. While here, also apply 'const' to a number of
objects and scalar parameters.
Original output:
The action ACT-01 evaluated to true at 2018/11/02 report:0.
New output:
Action ACT-01 triggered at 02-Nov-2018 00:00:00 (report interval 0 to 1).
