ICal DTSTART Parsing Issue for certain Repeating Events with Excluded Dates (EXDATE)

[Dan-Peck]

An internal issue affecting START dates for YEARLY repeating events, and MONTHLY, BY DAY repeating events was discovered when an EXDATE did not exclude an occurrence that it should have. (Dev Note: The T was not being added to the DTSTART string when $start_time was appended to event occurrences beyond the first instance.)

Here is a sample VEVENT entry that is affected by this scenario:

BEGIN:VEVENT
RRULE:FREQ=MONTHLY;UNTIL=20241220T170000Z;INTERVAL=1;BYDAY=3FR
EXDATE;TZID=Pacific Standard Time:20241115T090000
UID:0XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX0
 0XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
SUMMARY:EXDATE MONTHLY BY DAY TEST
DTSTART;TZID=Pacific Standard Time:20241018T090000
DTEND;TZID=Pacific Standard Time:20241018T093000
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20241115T164458Z
TRANSP:TRANSPARENT
STATUS:CONFIRMED
SEQUENCE:0
LOCATION:
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-BUSYSTATUS:FREE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DONOTFORWARDMEETING:FALSE
X-MICROSOFT-DISALLOW-COUNTER:FALSE
X-MICROSOFT-REQUESTEDATTENDANCEMODE:DEFAULT
X-MICROSOFT-ISRESPONSEREQUESTED:FALSE
END:VEVENT

Note: The most recent case exhibiting similar end-behavior is: #2246