The Daily Plan should schedule cyclic orders correctly across time zones

Current Situation

• Assume a schedule for orders with cyclic start times.
• If the schedule is configured for the UTC time zone and the Daily Plan is configured for some later time zone then orders scheduled for a time before midnight of the Daily Plan time zone are scheduled for the previous day. This behavior is correct, however, such orders carry different Order IDs depending on midnight of the Daily Plan time zone and therefore break the behavior of the Daily Plan.
• As a result such orders cannot be submitted.
• Explanation:
  • the main part of a cyclic order consists of #<day>#C<auto increment>-
    • e.g.:
      • #2022-01-11#C84186940203-00001-11-cyclic
      • #2022-01-11#C84186940203-00002-11-cyclic
  • in some cases generates Daily Plan the different <day> part for the same cyclic order:
    • #2022-01-10#C84186940203-00001-11-cyclic
    • #2022-01-11#C84186940203-00002-11-cyclic

Desired Behaviour
If the Schedule time zone and the Daily Plan time zone differ then the Daily Plan should consider to create the same fixed part of the Order ID for orders scheduled before and after midnight of the Daily Plan time zone.
 
Test instructions

• use Setting -> dailyplan -> time_zone = UTC
• create a workflow and a schedule with
  • custom Time Zone
  • Repeat Time: 01:00:00
  • Begin: 00:00:00
  • End: 08:00:00
• create Daily Plan for the next day for this schedule
  • check the Tooltip of the generated cyclic order:
    • Orders: <total> should correspond with the total info of the order id #<day>#C<auto increment>-<current>-<total>..
      • e.g.: Orders: 11 (#2022-01-11#C84186940203-00001-11-cyclic)