StefanKock

Current state: 1. `joda-time` is removed everywhere except in the `android-app`. -> to be done by @MartinWahnschaffe 2. Discussions solved, PR #9942 updated.

> A. Use API Level 26 as minimum - so no longer support Android 7 It's a product question whether it's an option to cancel support for older Android API...

It happens twice within 10 builds that the following test failed on Jenkins causing the CI to stop. ``` java.lang.AssertionError: Expected: but: was at de.symeda.sormas.api.task.TaskHelperTest.testGetDefaultDueDate(TaskHelperTest.java:24) ```

Fixed flaky test ( 67ef6dd)

Open question: Does keeping persons in-sync between instances makes sense?

If `@AroundTimeout` works (not sure, never used it, did not find an example that fits our use case), it might work to add the annotation to the existing `logAudit` method....

I don't see this happening or fixed in 1.72.0, and should probably converted to a change. Another option would also be to delete an event group when the last event...

1. We still need a hint what query is not performant enough 2. Was this ever retested with a more recent version? A lot changed since 1.70

I now found out that `DateHelper.getStartOf/getEndOf` methods implicitly converted `null` to `LocalDateTime.now()` and now many backend tests fail. I'm uncertain if this behaviour is desirable or not. ```java @Test public...

Other findings to be discussed: 1. Obsolete? `de.symeda.sormas.ui.utils.DateFilter` - DateHelper.findDateBounds - DateHelper.findDatePrefix 2. Relevance? `de.symeda.sormas.ui.EditFormLayoutCharting`