When we abort the replication process because we've got shard ranges and
the sharder is now responsible for ensuring object-row durability, we
log a warning like "refusing to replicate objects" which sounds scary.
That's because it *is*, of course -- if the sharder isn't running,
whatever rows that DB has may only exist in that DB, meaning we're one
drive failure away from losing track of them entirely.
However, when the sharder *is* running and everything's happy, we reach
a steady-state where the root containers are all sharded and none of
them have any object rows to lose. At that point, the warning does more
harm than good.
Only print the scary "refusing to replicate" warning if we're still
responsible for some object rows, whether deleted or not.
Change-Id: I35de08d6c1617b2e446e969a54b79b42e8cfafef
c0dbf5b885