zbigMapReduce.js should use a write concern for inserts so it does not roll over its oplog

zbigMapReduce.js can roll over its oplog if the inserts go fast enough and the fetching is a bit slow, leading to unrecoverable rollbacks. Reducing the data size to 50MB total or increasing the oplog size to 250 MB (or something in the middle) would be good.