.Net: Bug: FinishReason, Usage is null in StreamingChatMessageContent.MetaData post upgrade

[ssbhavesh]

Describe the bug
FinishReason and other metadata fields are null when GetStreamingChatMessageContentsAsync is invoked, but non null when GetChatMessageContentsAsync is invoked for the same payload.

To Reproduce
Steps to reproduce the behavior:

1. Initialize chatCompletionService.
2. Add some local plugins
3. Invoke chatCompletionService.GetStreamingChatMessageContentsAsync and chatCompletionService.GetChatMessageContentsAsync
4. response MetaData contains FinishReason field as null in case of GetStreamingChatMessageContentsAsync but "ToolCalls" in GetChatMessageContentsAsync which is correct expected value.
5. In production we are using Microsoft.SemanticKernel 1.15 and FinishReason value is tool_calls which is expected but is null after upgrade.
6. PromptExecutionSettings is as mentioned below:
   PromptExecutionSettings settings = new() { FunctionChoiceBehavior = Microsoft.SemanticKernel.FunctionChoiceBehavior.Auto(autoInvoke: false) };

Screenshots
GetChatMessageContentsAsync

GetStreamingChatMessageContentsAsync

Platform

• Language: c#
• Source: Microsoft.SemanticKernel (any version above 1.40)
• AI model: [e.g. OpenAI:GPT-4o-mini(2024-07-18)]
• IDE: [e.g. Visual Studio, VS Code]
• OS: [e.g. Windows, Mac]

Additional context
Add any other context about the problem here.