fix(cdk-assets): concurrent asset builds can leave a corrupted archive (

#23677)

Resolves #23290

A very simple fix for the issue where builds with `--concurrency` specified can lead to corrupt archives. Rather than use the outputFile as the basis for the temp file name we simply use a random UUID.

Please note that I was unable to run the integration tests in this instance, which are likely necessary given that this change impacts the behavior of the archiver.

packages/cdk-assets/lib/private/archive.ts

@@ -11,7 +11,7 @@ type Logger = (x: string) => void;
 export async function zipDirectory(directory: string, outputFile: string, logger: Logger): Promise<void> {
   // We write to a temporary file and rename at the last moment. This is so that if we are
   // interrupted during this process, we don't leave a half-finished file in the target location.
-  const temporaryOutputFile = `${outputFile}._tmp`;
+  const temporaryOutputFile = `${outputFile}.${randomString()}._tmp`;
   await writeZipFile(directory, temporaryOutputFile);
   await moveIntoPlace(temporaryOutputFile, outputFile, logger);
 }
@@ -96,4 +96,8 @@ async function pathExists(x: string) {
     }
     throw e;
   }
+}
+
+export function randomString() {
+  return Math.random().toString(36).replace(/[^a-z0-9]+/g, '');
 }