Fallback to slower consistency verification when store timestamp < log timestamp

In this situation there is a possibility that the last transaction log consistent timestamp is an uncommitted transaction (i.e. response not written successfully in storage). We must compare the timestamp of the last committed transaction in this situation.

Fix #189