Batch sets should replace in L1 instead of invalidate

[ScottMansfield]

the set, add, and replace commands should do a replace in L1 instead of a delete in the batch orchestrator. This is for users that are actually using the service when their data is replaced. If we know their data is in L1, we can keep it hot. For users not using the service, whose data is cold in L2, we don't set in L1.