When locking is disabled, CachedOnDiskCorpus will fail if a file already exists for a testcase

[s1341]

When the locking functionality is disabled, CachedOnDiskCorpus just uses the input hash as the testcase name. If the file already exists though, the write_file_atomic will fail killing the fuzzer.

This shouldn't happen. If the file already exists, we should simply not write it. If you are worried about hash collisions, don't disable the locking functionality.