REPL local iteration optimization cannot be used when store has write behind

When write behind is enabled, the write modification is stored on the primary owner. REPL local iteration can read from non owned data, thus causing an inconsistency.

Thus distributed streams should always go remote when not all segments are primarily owned on a given node when write behind is enabled.