Mapreduce should not create collections with duplicate IDs

If a mapreduce is run while downgrading to compatibility version 3.4 (but before UUIDs are removed), and the final output collection exists, the new temporary collection will have the same UUID as the old final output collection. We should clear the options.uuid field whenever we do not set it explicitly.