.Net Agents - History Management Consistency: ChatCompletionAgent

[crickman]

The direction invocation (no chat) case for ChatCompletionAgent requires the user to manually update the ChatHistory with the agent response. This isn't required for the streaming case or any usage of OpenAIAssistantAgent.

Even worse, the Termination scenario for IAutoFunctionInvocationFilter and manual function calling cases require complex, non discoverable logic to avoid introducing invalid changes to the ChatHistory.

Having ChatCompletionAgent.InvokeAsync fully manage the history not only is consistent with the rest of the Agent Framework, it solves this advance, non-discoverable cases.