Handle resent sync commands with server-side changes

If the client sends the same sync-key twice, the response should be the
same. The previous implementation would only sent added entries once,
but not the second time, meaning a client would miss these updates (and
potentially trigger duplicate content id errors on the server).