Updated ical4j to `3.2.10`

[ArnyminerZ]

Edit: Does not fix https://github.com/ical4j/ical4j/issues/454, does not fix https://github.com/bitfireAT/davx5/issues/165

[leonggs]

Recently, I've imported a third-party ics file to my Nextcloud calendar containing SEQUENCE:2302221158. It misuses the sequence field as booking date or something like that. All implementations such as ical4j that conform to the iCalendar RFC standard might fail parsing this encoding as 32 bit signed integers since 01.01.2022. Dear third-party, you have constructed a year2k, seriously? :D

• Nextcloud Calendar doesn't discard this standard-violating event, which I expect my calendar apps to do!
• Davx 4.3-ose does and displays an inconvenient error in the notification bar containing net.fortuna.ical4j.data.ParserException in its stack trace. For average users it's probably not possible to identify the problematic remote resource/event that causes that error.

Do this fix in the current issue fix my problem described above as well and will they be in the next release of Davx without further actions?

[rfc2822]

Shall we merge it although it does not fix the original problem?

[ArnyminerZ]

Mmmh... Maybe... It's always good to have dependencies updated, there might be other bugfixes

[rfc2822]

Agree…

There's a failing test though.

[ArnyminerZ]

The failing test is annotated with "should not fail in future", so it must have been fixed 😄

[rfc2822]

Ah, nice, seems that it fixes a Persian Locale bug. Please keep the test to be sure in the future and just remove the failure expectation :)