Actually add an Azure event listener (#167)

Without a configured listener, we get no info on console.

With it, we get a LOT of useful diagnostics, including burning questions like "what did DefaultAzureCredential actually do?"

Author: directhex

src/Microsoft.SourceIndexer.Tasks/DownloadStage1Index.cs

@@ -3,6 +3,7 @@
 using System.Linq;
 using System.Text;
 using Azure;
+using Azure.Core.Diagnostics;
 using Azure.Identity;
 using Azure.Storage.Blobs;
 using Azure.Storage.Blobs.Models;
@@ -54,6 +55,8 @@ private void ExecuteCore()
                 StorageAccount = "https://" + StorageAccount + ".blob.core.windows.net";
             }
 
+            using AzureEventSourceListener listener = AzureEventSourceListener.CreateConsoleLogger();
+
             DefaultAzureCredential credential;
             DefaultAzureCredentialOptions credentialoptions;
 

src/UploadIndexStage1/Program.cs

@@ -6,6 +6,7 @@
 using System.Text;
 using System.Threading.Tasks;
 using Azure.Core;
+using Azure.Core.Diagnostics;
 using Azure.Identity;
 using Azure.Storage.Blobs;
 using Azure.Storage.Blobs.Models;
@@ -65,6 +66,8 @@ static async Task Main(string[] args)
                 storageAccount = "https://" + storageAccount + ".blob.core.windows.net";
             }
 
+            using AzureEventSourceListener listener = AzureEventSourceListener.CreateConsoleLogger();
+
             DefaultAzureCredential credential;
             DefaultAzureCredentialOptions credentialoptions;