42383 temporary update cdt datastore documentation and td replicator stop regarding fire and forget replication

well... the queueing parts from the TDReplicatorManager are still in place. Technically, I think it sorta queues, but its guaranteed that nothing is in the queue except each particular replicator's work, which runs in a block. It's left over from the manager. I did as little work as necessary to move the threading code from the manager to each individual replicator, since we wanted to make this transition in stages.  

I'm looking into removing this queue.