Fix not firing data changed event on replace item

[r-dunning]

Firing the Data Changed event where the event writes to the same stream in a transactional batch would result in conflicts as the next event to be processed in the batch would conflict on Ids. I've added support for the ContainerMock to take a param on update methods whether to immediately invoke a registered DataChanged event, or queue the invoke. The TestTransactionalBatch will update with the param set to Batch, then process the queued DataChanged events its self.
This also more closely aligns what would happen in cosmos as any CFPS are most likely to receive their events after the stream has already returned
Other fix:

• Fix not firing data changed event on replace item