Disable Rebase for Objects that Trigger +2 Errors

[jleandroperez]

We're seeing a loop in which:

1. Client sends local changes to the backend.
2. On Error (405 / 417 / 440), the full object's data will get sent to the backend.
3. Full data message from the previous step gets rejected.
4. ReIndex kicks in.
5. Local pending changes get rebased
6. Back to step 1.

As a counter measure, let's selectively disable the rebase mechanism for those objects that go through step 3.

This loop is probably related to Issue #314

Backend Logs:

    client sends change (sv=9489),
    server rejects with 440,
    client sends change (sv=9489, d=fulldata),
    server accepts,
    client sends change (sv=9489),
    server rejects 440,
    client sends change (sv=9489, d=fulldata),
    server accepts,
    client sends change (sv=9489),
    server rejects 440,
    client sends change (sv=9489, d=fulldata),
    server rejects 412,
    client appears to re-index,
    client sends change (sv=9489),
    server rejects 440,
    client sends change (sv=9489, d=fulldata),
    server rejects 412

/cc @fredrocious