Use UUID to unique response file names, instead of content hash

We've been having issues with content hash causing collisions as well as issues with underlying Foundation atomic APIs. For now, attempt to simply make the files unique with a uuid.

Author: artemcm

Sources/SwiftDriver/Execution/ArgsResolver.swift

@@ -11,6 +11,7 @@
 //===----------------------------------------------------------------------===//
 
 import class Foundation.NSLock
+import struct Foundation.UUID
 
 import func TSCBasic.withTemporaryDirectory
 import protocol TSCBasic.FileSystem
@@ -189,14 +190,13 @@ public final class ArgsResolver {
       (job.supportsResponseFiles && !commandLineFitsWithinSystemLimits(path: resolvedArguments[0], args: resolvedArguments)) {
       assert(!forceResponseFiles || job.supportsResponseFiles,
              "Platform does not support response files for job: \(job)")
-      // Match the integrated driver's behavior, which uses response file names of the form "arguments-[0-9a-zA-Z].resp".
-      let hash = SHA256().hash(resolvedArguments.joined(separator: " ")).hexadecimalRepresentation
-      let responseFilePath = temporaryDirectory.appending(component: "arguments-\(hash).resp")
+      let uuid = UUID().uuidString
+      let responseFilePath = temporaryDirectory.appending(component: "arguments-\(uuid).resp")
 
       // FIXME: Need a way to support this for distributed build systems...
       if let absPath = responseFilePath.absolutePath {
         let argumentBytes = ByteString(resolvedArguments[2...].map { $0.spm_shellEscaped() }.joined(separator: "\n").utf8)
-        try fileSystem.writeFileContents(absPath, bytes: argumentBytes, atomically: true)
+        try fileSystem.writeFileContents(absPath, bytes: argumentBytes)
         resolvedArguments = [resolvedArguments[0], resolvedArguments[1], "@\(absPath.pathString)"]
       }