Fixing handling of deletes in ApplyAndFilterDeletesFilter

It was causing an infinite loop when there were duplicate CFs added to the filter.
Further, it wasn't handling the delete/put ordering correctly, which later lead
to incorrect indexes being constructed in the tests.

Allows removal of the "destroy tables" stuff in MutableIndexTest, since handle the Phoenix 'table delete' tombstones properly.