[Backport to CMS 11.1, 11.2 and 10.2] Patched Jackrabbit LockManagerImpl is not fully honoring the JCR API

REPO-1381 intruced a new 'lazy' or 'just-in-time' expiration handling of JCR locks, thereby no longer needing the Jackrabbit default background thread monitoring and removing possibly expired locks.

However, that customization currently does not honor a few JCR Lock API method usages: #isLive() and #getSecondsRemaining(), and which actually fail when running the Jackrabbit integration tests.

Furthermore the internal (within LockManagerImpl) boolean #unlockIfExpired(LockInfo) method is incorrectly used in several places to (also) check if a lock is 'live'. Which may cause a false positive effect.

With this improvement issue those problems need to be solved and replace the current used REPO-1381 'patch' in building the Hippo specific Jackrabbit version, starting with Jackrabbit-2.14.0.