Update SDK name in CHANGELOG.md

[rahuldevikar761]

No description provided.

[Copilot]

Pull request overview

This PR updates the CHANGELOG.md to replace legacy "Kairo" references with the current "Agent 365" SDK name, ensuring consistency with the project's current naming conventions.

Changes:

• Updated the top-level SDK description from "Microsoft Kairo SDK" to "Microsoft Agent 365 SDK"

Comments suppressed due to low confidence (5)

CHANGELOG.md:11

• The package name still contains "Kairo" and should be updated to use "Agent 365" terminology. This is a legacy reference that needs to be updated according to the project's naming guidelines which specify that all "Kairo" references should be removed or replaced.

- **Microsoft.Kairo.Sdk.DevTools.Analyzer.SemanticKernel** - Comprehensive Roslyn analyzer package for enforcing Agent365 governance patterns

CHANGELOG.md:34

• This SDK name reference still uses "Kairo" and should be updated to "Microsoft Agent 365 SDK" for consistency with the updated description at line 3.

- Initial release of Microsoft Kairo SDK

CHANGELOG.md:36

• The extension method name reference uses "Kairo" and should be updated to reflect the current Agent 365 SDK naming conventions.

- `Kairo` extension methods for `IHostApplicationBuilder` configuration

CHANGELOG.md:37

• The class name "KairoSpanProcessor" contains the legacy "Kairo" keyword and should be documented using the updated naming convention consistent with Agent 365 SDK.

- `KairoSpanProcessor` for custom span processing with agent-specific metadata

CHANGELOG.md:41

• The class name "KairoOpenTelemetryScope" contains the legacy "Kairo" keyword and should be documented using the updated naming convention consistent with Agent 365 SDK.

  - `KairoOpenTelemetryScope` base class for extensible tracing