Integrate character_map / UnicodeEncodeError paths with delete operation feature

[alanking]

Requires #48 to be completed first.

[alanking]

I think we need to do this sooner rather than later. Syncing with a delete mode defined results in data at translated (read: character-mapped or UnicodeDecodeError-handled) paths getting deleted unexpectedly.

[trel]

Hmm, can character_map and delete be detected and declared incompatible?

That doesn't really help with the UnicodeDecodeError cases...

[alanking]

Right. The options I discussed with @korydraughn were...

1. Just implement the support (Integrate character_map / UnicodeEncodeError paths with delete operation feature #261, this issue). This will take some effort.
2. Detect and prevent. This is easy enough for character_map. From what I can tell, the amount of effort to do this for the UnicodeEncodeError case would be high enough that we might as well just implement the support.
3. Punt. Delete Mode is a new feature and we are still pre-1.0, so "Use at your own risk."

We wanted 2 to be easy, but I don't think it will be much less effort than 1. 3 is indefensible given the high risk of data loss.

[trel]

That assessment seems correct to me.

[korydraughn]

Let's give it a try and implement option 1.

[alanking]

After I started implementing this, I found that option 2 was actually quite easy. We are just going to do that and kick this back to 0.7.0. Sorry for turbulence.