Clustered Expiration can deadlock with Pessimistic Tx on a non owner

Pessimistic tx first lock a key before doing an operation. This is true of non owners as they will first lock the key on the owner then possibly retrieve the previous value in a subsequent call. Related to ISPN-12332. If the retrieved key is expired we will then attempt to remove it, but it will deadlock as the invoking code already has the lock and expiration is done outside of the current transaction.

Instead we must pass along the fact that the invoking code has the lock, similar to how we perform locking differently when a non tx write sees an expired entry. IF ISPN-12332 is fixed this issue is no longer needed, but that may take more time and may not be implemented.