All calls to JsonSerializer.Serialize should use JsonSerialisationOptions.Options

[SteveBush]

Describe the bug

In constructing the Brighter service host, I add my JsonConverters to JsonSerialisationOptions.Options.Converters. I use these converters to serialize/deserialize Brighter messages. Unfortunately, there are instances of JsonSerializer.Serialize in the code (e.g., RequestLoggingHandler and RequestLoggingHandlerAsync) that doesn't include JsonSerialisationOptions.Options in calls to JsonSerializer.Serialize and JsonSerializer.Deserialize. When logging the request, the serialization fails. Similar behavior for BrighterTracer.

I'm happy to make these changes in a PR.

To Reproduce

Steps to reproduce.

1. Create a Request message with an IPAddress as a public field.
2. Post the Request to an Inbox with request logging;
3. RequestLoggingHandler.LogCommand fails to serialize the request.

Fix

Update all calls to JsonSerializer.Serialize and JsonSerializer.Deserialize to include JsonSerialisationOptions.Options.

• RequestLoggingHandler
• RequestLoggingHandlerAsync
• BrighterTracer
• MQTTMessageConsumer
• MQTTMessagePublisher

Exceptions (if any)

Further technical details

• Brighter version: 10.

[iancooper]

@SteveBush Thanks for this, we will pick up this bug for V10 as requested. Feel free to raise a PR if you want.