Request: display end date of *updateEventLaunchDelay entries in logs

[securitygeneration]

When an *updateEventLaunchDelay key is set and the current date is still within the macOS release date + LaunchDelay window, Nudge does not launch.

Currently Nudge logs an Informational log event when this condition exists, stating:

Device within nudgeMinorUpdateEventLaunchDelay

However this does not give an admin an indication of when Nudge will actually trigger for that log event's device. To make this clearer, it would be good to augment the log to include the end date of the LaunchDelay, e.g.:

Device within nudgeMinorUpdateEventLaunchDelay (until <end date>)

Bonus request: as the current log is Informational, it does not appear in the nudge.log file. Given this file is commonly output when debugging Nudge, it may be beneficial to admins to promote these events to normal log items so they can more easily understand why Nudge does not activate when they might be expecting it to.

[erikng]

fixed here 7373cbf

the bonus is fixed too :)