TEPHRA-43 TransactionVisibilityFilter can prematurely drop delete markers

This fixes all versions of TransactionVisibilityFilter so that we only drop "delete" tombstones (Puts with empty values) when all store files are being read at the same time.  Makes the following changes:
* adds a flag to TransactionVisibilityFilter, set when doing a user scan or major compaction
* adds a test case that verifies "delete" tombstones are kept after a memstore flush
I wonder does it make sense to move logic of determining clearDeletes based on ScanType in extra ctor in TransactionVisiblityFilter