Move to 'Azure.Identity' v1.14.2 and refactor the telemetry library

[daxian-dbw]

PR Summary

Fix #393

I can reproduce this issue on macOS with the error from AzurePowerShellCredential() being "PowerShell did not return a valid response." This turns out to be an issue with the Azure.Identity library (Azure/azure-sdk-for-net#50578). After moving to the latest 1.14.2 of the package, it works for me on macOS.

---

However, moving to the 1.14.2 of the Azure.Identity caused a dependency conflict with the Microsoft.ApplicationInsights.WorkerService package, which brings in an older version of Microsoft.Extensions.DependencyInjection that conflicts with the newer version of Microsoft.Extensions.DependencyInjection.Abstractions that comes with Azure.Identity.

In fact, we should not depend on Microsoft.ApplicationInsights.WorkerService, but instead should use Microsoft.ApplicationInsights directly. The WorkerService package was designed for ASP.NET Core applications that need automatic dependency injection, performance counters, and various auto-collectors. For a simple console application that just needs to send traces and exceptions to Application Insights, the core Microsoft.ApplicationInsights package is perfect and much more appropriate.

What were changed: (summarized by GitHub Copilot)

• Replaced Microsoft.ApplicationInsights.WorkerService with just Microsoft.ApplicationInsights
• Simplified the telemetry initialization from a complex DI setup to a simple direct instantiation
• Used modern TelemetryConfiguration.CreateDefault() with connection string instead of deprecated approaches

Benefits of the change: (summarized by GitHub Copilot)

• Dramatically reduced dependencies - We went from 67+ transitive packages to about 25
• Eliminated version conflicts - No more conflicting DI framework versions
• Simpler code - The constructor is now much cleaner and easier to understand
• Faster build times - Fewer packages to restore and compile
• Smaller deployment - Much lighter runtime footprint
• Same functionality - You still get exactly the same telemetry capabilities

[Copilot]

Pull Request Overview

This PR addresses a macOS authentication issue by upgrading Azure.Identity to v1.14.2 and refactors the Application Insights telemetry implementation to resolve dependency conflicts.

• Upgrades Azure.Identity from v1.11.4 to v1.14.2 to fix AzurePowerShellCredential authentication issues on macOS
• Replaces Microsoft.ApplicationInsights.WorkerService with the core Microsoft.ApplicationInsights package to eliminate dependency conflicts
• Simplifies telemetry initialization by removing complex DI setup in favor of direct TelemetryClient instantiation

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
Microsoft.Azure.Agent.csproj	Updates package references to Azure.Identity v1.14.2 and Microsoft.ApplicationInsights v2.23.0
Telemetry.cs	Refactors telemetry initialization to use direct instantiation instead of dependency injection framework

[isra-fel]

LGTM thanks!