Handle NuGet.Config and ProdCon.txt missing

That's not really likely to happen, unless the SSL/HTTP stack itself is
broken. But if that's the case, the runner should try and continue
without the extra configuration.

It's possible to run into this if OpenSSL 3.0 is the system OpenSSL
library and .NET (using OpenSSL 1.1) has some problems using the OpenSSL
3.0 configuration at /etc/ssl/openssl.conf.

Also use Exception.ToString() everywhere to see the full exception stack
traces.

README.md

@@ -165,6 +165,10 @@ Some notes for writing tests:
 
  $ git push --tags remote-name
 
+ OR, better:
+
+ $ git push remote-name tag-name
+
 3. GitHub Actions will create a draft release corresponding to the tag.
 
  It will also attach the `turkey` and `turkey-$arch` binaries to the release.

Turkey/Program.cs

@@ -150,8 +150,7 @@ public static async Task<string> GenerateNuGetConfigIfNeededAsync(string additio
  catch( HttpRequestException exception )
  {
  Console.WriteLine("WARNING: failed to get ProdCon url. Ignoring Exception:");
- Console.WriteLine(exception.Message);
- Console.WriteLine(exception.StackTrace);
+ Console.WriteLine(exception.ToString());
  }
 
  string nugetConfig = null;
@@ -162,11 +161,13 @@ public static async Task<string> GenerateNuGetConfigIfNeededAsync(string additio
  catch( HttpRequestException exception )
  {
  Console.WriteLine("WARNING: failed to get NuGet.config from source-build. Ignoring Exception:");
- Console.WriteLine(exception.Message);
- Console.WriteLine(exception.StackTrace);
+ Console.WriteLine(exception.ToString());
  }
 
- return await nuget.GenerateNuGetConfig(urls, nugetConfig);
+ if (urls.Any() || nugetConfig != null)
+ {
+ return await nuget.GenerateNuGetConfig(urls, nugetConfig);
+ }
  }
 
  return null;

Turkey/SourceBuild.cs

@@ -52,7 +52,7 @@ public async Task<string> GetNuGetConfigAsync(Version version)
  }
  catch( HttpRequestException e )
  {
- Console.WriteLine($"WARNING: {e.Message}");
+ Console.WriteLine($"WARNING: {e.ToString()}");
  }
 
  return nugetConfig;