Ignore 409s from putback when db == skim
Ignore 409s from putback when db == skim

Eventually, the write that caused the conflict will show up in
the _changes feed, so we can just ignore 409s when the source
database and skim database are the same.

Not clear what the best course of action is when they're not the same
Merge?

npm/npm-skim-registry