Handle an invalid value for trigger duration gracefully

[kesselb]

Steps to reproduce

1. Open outlook.com
2. Create a new event
3. Pick "At time of event" as reminder
4. Invite an external attendee

Expected behavior

It should be possible to parse the calendar invitation

Actual behavior

Parsing the calendar invitations fails

Error: invalid duration value: Not enough duration components in ""
    icalduration_from_string ical.js:4153
    decorate ical.js:811
    _decorate ical.js:2957
    _hydrateValue ical.js:2940
    getFirstValue ical.js:3086

Library version

No response

Additional info

Georg's recommendation:
kewisch/ical.js#400 (comment)

Example event:

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:W. Europe Standard Time
BEGIN:STANDARD
DTSTART:16010101T030000
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T020000
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Bob:mailto:bob@example.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=alice@example.org:mailto:alice@example.org
DESCRIPTION;LANGUAGE=en-US:\n
UID:100020003000
SUMMARY;LANGUAGE=en-US:Remind me test
DTSTART;TZID=W. Europe Standard Time:20250219T080000
DTEND;TZID=W. Europe Standard Time:20250219T083000
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20250211T161355Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:2123520737
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-DONOTFORWARDMEETING:FALSE
X-MICROSOFT-DISALLOW-COUNTER:FALSE
X-MICROSOFT-REQUESTEDATTENDANCEMODE:DEFAULT
X-MICROSOFT-ISRESPONSEREQUESTED:TRUE
X-MICROSOFT-LOCATIONS:[]
BEGIN:VALARM
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:P
ACTION:DISPLAY
END:VALARM
END:VEVENT
END:VCALENDAR

[st3iny]

Outlook seems to set invalid alarms with a trigger value of P instead of PT0S or P0D. We could add another repair step to fix those and then continue parsing as usual.