Consider adding AssertJ-style fluent assertions test utility

[sleberknight]

For example, assume there is a ApplicationErrorAssertions with a method assertThatApplicationError:

var error = ApplicationErrorVerifications.verifyExactlyOneInsertOrIncrement(errorDao);
assertThatApplicationError(error)
        .hasDescription("an I/O error occurred: no such file /data/foo.txt")
        .hasExceptionType(UncheckedIOException.class)
        .hasExceptionCauseType(NoSuchFileException.class)
        .hasExceptionCauseMessage("/data/foo.txt")
        .hasStackTraceContaining("readFile")
        .hasNumTimesOccurred(1)
        .isNotResolved()

The main disadvantage compared to using JUnit's assertAll is that the above stops at the first assertion failure.