When logging errors, also log payload

[kzu]

This helps diagnose the actual issue, since it usually stems from the payload we're trying to send, and just the response error wouldn't be enough to diagnose and fix.

[kzu]

🧪 Details on Ubuntu 24.04.2 LTS

from dotnet-retest v0.7.1 on .NET 8.0.17 with 💜 by @devlooped

[Copilot]

Pull Request Overview

This PR enhances error logging by including the outgoing payload alongside the HTTP response error, making debugging of failed WhatsApp API calls easier.

• Introduced jsonOptions to standardize JSON serialization settings.
• Changed error handling to serialize both payload and parsed response into a single JSON block.
• Updated the logger and exception to include the serialized payload context.

Comments suppressed due to low confidence (2)

src/WhatsApp/WhatsAppClient.cs:68

• [nitpick] The variable name error is ambiguous and matches the serialized property name. Consider renaming it to errorDetailsJson and using a more specific property name like responseError for clarity.

var error = JsonSerializer.Serialize(new

src/WhatsApp/WhatsAppClient.cs:70

• Logging the raw payload may expose sensitive data. Ensure that any personal or confidential fields are redacted or filtered before logging in production.

payload,

[Copilot]

Parsing the HTTP response content without handling parse errors could throw an exception if the content isn’t valid JSON and mask the original failure. Consider wrapping the parse call in a try/catch and falling back to the raw string on parse errors.