Debug dotnet new timeouts

- hang long enough to grab a dump

This will _not_ help us understand later inability to acquire `DotNetNewLock`
- guessing but this might have something to do w/ the 20 minute default timeout for that acquisition

Author: dougbu

src/ProjectTemplates/Shared/Project.cs

@@ -102,10 +102,19 @@ internal async Task<ProcessResult> RunDotNetNewAsync(
             try
             {
                 Output.WriteLine("Acquired DotNetNewLock");
+
                 // Temporary while investigating why this process occasionally never runs or exits on Debian 9
                 environmentVariables.Add("COREHOST_TRACE", "1");
-                using var execution = ProcessEx.Run(Output, AppContext.BaseDirectory, DotNetMuxer.MuxerPathOrDefault(), argString, environmentVariables);
+
+                using var execution = ProcessEx.Run(
+                    Output,
+                    AppContext.BaseDirectory,
+                    DotNetMuxer.MuxerPathOrDefault(),
+                    argString,
+                    environmentVariables,
+                    TimeSpan.FromHours(5));
                 await execution.Exited;
+
                 return new ProcessResult(execution);
             }
             finally