GH-1906 - Allow resubmitting least recently attempted failed publications first

[AdzerKI]

Closes #1906.

ResubmissionOptions.withLeastRecentlyAttemptedFirst() makes findFailedPublications(…) return the least recently attempted publications first: ordered by lastResubmissionDate, falling back to publicationDate for publications that were never resubmitted. The option reaches the repositories through FailedCriteria. JDBC and JPA use COALESCE in the query, Neo4j coalesce(…) in Cypher, MongoDB an aggregation with $ifNull as a plain sort can't express the fallback. Without the option, failed publications are still read oldest first.

With the option, a publication that was just resubmitted and failed again moves to the end of the queue, so publications that keep failing or are skipped by the resubmission filter no longer keep the others from being read.

Each repository test suite gets a test resubmitting the older of two failed publications and expecting it first by default and the newer one first with the option, in a batch of one. A registry unit test checks that the option ends up in FailedCriteria. events.adoc describes the default order and the option. The JDBC tests pass on H2, HSQLDB, PostgreSQL, MySQL, MariaDB, SQL Server and Oracle, the JPA, MongoDB and Neo4j suites pass as well.

[AdzerKI]

Reworked as discussed in #1906: the new order is now opt-in through ResubmissionOptions.withLeastRecentlyAttemptedFirst(), and failed publications are still read oldest first by default.