Deliver latest lazy rendition even if stale stored rendition exists

The fix for NXP-23266 introduced the undesirable behavior described in the following unit test comment for org.nuxeo.ecm.platform.rendition.service.lazy.TestDeliverStaleLazyRenditions.testStoredLazyRenditions():

    // If a stored stale rendition exists, asking for a stored rendition will never return an up-to-date rendition
    // as shown by the previous call, so not calling checkUpToDateRendition

Once an up-to-date lazy rendition has been generated, it should be returned. Currently, lazy rendition delivery is always one revision behind once a stored rendition exists. This is a Critical regression that significantly changes lazy stored rendition delivery behavior in an unexpected manner. The introduction of the "stale" marker and "stale" rendition delivery was intended to increase rendition delivery granularity, not prevent delivery of the most up-to-date lazy rendition revision.