Remove exception throw for unsuccessful HTTP responses in SendChatHistoryAsync

[Copilot]

The SendChatHistoryAsync implementation threw InvalidOperationException on unsuccessful HTTP responses, contradicting the interface contract which states: "HTTP exceptions are caught and logged but not rethrown. The method will complete successfully even if the HTTP request fails."

Changes

• Removed exception throw on non-success HTTP status codes - replaced with direct error logging
• Restructured control flow - moved success log into else block for clarity

Before

if (!response.IsSuccessStatusCode)
{
    var errorContent = await response.Content.ReadAsStringAsync();
    throw new InvalidOperationException(
        $"Failed to send chat history. Status: {response.StatusCode}, Error: {errorContent}");
}
this._logger.LogInformation("Successfully sent chat history to MCP platform");

After

if (!response.IsSuccessStatusCode)
{
    var errorContent = await response.Content.ReadAsStringAsync();
    this._logger.LogError("Failed to send chat history. Status: {StatusCode}, Error: {ErrorContent}", 
        response.StatusCode, errorContent);
}
else
{
    this._logger.LogInformation("Successfully sent chat history to MCP platform");
}

The exception was being caught by the general exception handler and logged anyway - this eliminates the redundant throw/catch cycle and aligns behavior with documentation.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.