Daily Plan Service - logging improvement

Current Situation

• The Daily Plan Service logs information about the Schedules/Calendars in use and the corresponding orders created.
• However, the Schedule paths are concatenated in each subsequent log line, causing increased log file size and hindering the readability of the log, for example:

  ...
  ...[calculateStartTimes][js7][2023-12-22][schedule=/a][WorkingDaysCalendar=a,timeZone=Europe/Berlin]0 planned orders
  ...[calculateStartTimes][js7][2023-12-22][schedule=/a][schedule=/b][WorkingDaysCalendar=a,timeZone=Europe/Berlin]0 planned orders
  ...[calculateStartTimes][js7][2023-12-22][schedule=/a][schedule=/b][schedule=/c][WorkingDaysCalendar=a,timeZone=Europe/Berlin]0 planned orders
  ...
  

• Moreover, the protocol misses details about NonWorkingDay calendars in use.

Desired Behavior

• The output of the Daily Plan Service should be more clear, readable, and should avoid redundant information, for example:

  ...
  ...[calculateStartTimes][js7][2023-12-22][schedule=/a][WorkingDaysCalendar=a,timeZone=Europe/Berlin]0 planned orders
  ...[calculateStartTimes][js7][2023-12-22][schedule=/b][WorkingDaysCalendar=a,timeZone=Europe/Berlin]0 planned orders
  ...[calculateStartTimes][js7][2023-12-22][schedule=/c][WorkingDaysCalendar=a,timeZone=Europe/Berlin]0 planned orders
  ...
  

• The INFO and DEBUG log levels should provide more detail about NonWorkingDay calendars.