Changes the CDTReplicator.state property to be equal to CDTReplicatorSta...


If the replication was stopped via a call to CDTReplicator -stop, the status should be 'Stopped'. Otherwise, if
the replication stops on its own because it completes, the status is set to CDTReplicatorStatusComplete.

Changes the CDTReplicator code to clarify the object's state,
progress (changesTotal and changesProcessed), and messages sent to delegates
during start, stop and updates to the replicator.

Adds tests in ReplicationAcceptance using a delegate to stop replication
immediately after starting.
I see what you're saying.... am making this a switch-block now for clarification and accuracy.

The tricky bit is that there are times when TDReplicator can be in a non-fatal error state without immediate notification. But the developer could have called -stop on her own; perhaps their code detects the same or related non-fatal error. Nevertheless, we should report the error state if tdreplicator.error is true... 

We may want to write some interesting tests written to verify / determine any ambiguities -- the tests would have to start a local couchdb server and kill it off mid-replication.