ENG-5471: Merge canSafelyFreeTuple with notifyTupleDelete in all the table
stream contexts.

When a tuple delete undo action is released, all contexts will be notified and
they can make the decision of whether the tuple should be freed immediately or
not.

The COW context may stop a tuple from being freed immediately, but the tuple
should still be removed from the elastic context.
ENG-5471: Check if a tuple is pending delete before materializing it from the
elastic context.

If the tuple is deleted but pending snapshot, it shouldn't appear in the elastic
read context.
ENG-5471: Fix incorrect if condition in ElasticIndexReadContext.
ENG-5471: Crash if the site tries to materialize a deleted tuple from the
elastic index. It should be unpossible.
ENG-5283 distinct exit status.
ENG-5283 fix for csvloader exit code change.
For ENG-4904, make SnapshotDaemon not give up if there are failure responses
For ENG-4904, remove the failure state completely
Merge pull request #961 from VoltDB/ENG-5471

ENG-5471: Delete tuple from elastic index on tuple removal
ENG-5283 review changes.
ENG-5283 noise.
ENG-5283 keep 2 statuses for now.
Merge pull request #965 from VoltDB/ENG-5283

Eng 5283
For ENG-4904, always wait
For ENG-4904, demote messages to warn
ENG-5471: Call deleteTupleFinalize() when rolling back inserts.

deleteTupleFinalize() actually takes care of notifying the table streamer
now. To remove the tuple from the contexts on insert rollback, it needs to fall
through this instead of releasing the tuple memory directly.
For ENG-5523, fix SimpleClientResponse adapter to allow callback reuse and pick up multiple responses
Merge pull request #966 from VoltDB/ENG-4904

Eng 4904 Never gonna give you up on auto snapshots
Merge pull request #967 from VoltDB/ENG-5471

ENG-5471: Call deleteTupleFinalize() when rolling back inserts.
For ENG-5523, works better when you don't drop callback on the floor