MongoDB 3.6 adds UUIDs to uniquely identify collections.

General requirements:

• Tools need to be able to restore collections with their original UUIDs when requested
• When restoring from oplog to collection with new UUIDs, must translate old collection UUIDs to new collection UUIDs

More details (copied from TOOLS-1862):
For mongorestore:

• Add a --preserveUUIDs flag (TOOLS-1817 – may come after 3.6 GA unless we can fit it in)
• With --preserveUUIDs, have the following behaviors:
  • Require the --drop flag or abort
  • Require collection metadata to contain UUID info or abort
  • Require the destination to be in FCV 3.6 or abort (MUST check both ways that FCV could appear)
  • Create collections with the desired UUID with a synthesized applyOps command
    • Follow procedure in SERVER-31906 for creating admin.system.version with a given UUID
  • Apply oplog without modification