Importing Calendar Events with unparsable alarm trigger time results in misleading error

[wrdhub]

Trying to import a calendar event with an alarm trigger that our parser does not like results in a dialog telling the user the file is unreadable. In reality the file is readable, and the event(s) can be read just fine. It's really just an alarm trigger that is not being read correctly.

We should do one or both of these things:

1. Import the event and tell the user the alarm is not added.
2. Improve our alarm trigger parser. We used to have more restricted notification times that I think resulted in the way the parser works, but since added custom times were added I think it should not be so restrictive anymore.

Test notes

• Import calendar events with notifications, see that they are imported with the correct time.