DatabaseSagaSchema should honour opts.UseNewtonsoftForSerialization

[xwipeoutx]

Is your feature request related to a problem? Please describe.
I am using the Lightweight SQL Saga storage, and I got serialization errors when trying to persist my saga.

My saga has all the same types as my messages, so this surprised me - I realise now opts.UseNewtonsoftForSerialization doesn't actually apply to the saga storage, just to the messages. Saga storage will just use System.Text.Json regardless.

Describe the solution you'd like
I would like DatabaseSagaSchema to honour the global serialization settings.

Alternatively, provide a way to configure this particular serialization

Describe alternatives you've considered
In practice, I will use the EF Core saga persistence. I was hoping to have a shortcut for some early prototyping though. Oh well!

Additional context

I'm spiking out converting an NSB-backed application (big ol' monolith) to Wolverine, as I think we'll have much better flexibility. So this isn't yet for production use.

[jeremydmiller]

@xwipeoutx You're the very first person to ever care about that, but I get that you're coming from legacy code here. In real usage though, you'd want to use the EF Core integration so the DB commands are batched up w/ whatever else you're doing w/ EF Core.

Another alternative would be to use Marten instead, but I realize that's a bigger change.

I would be happy to accept a pull request enabling you to use Newtonsoft with the lightweight saga, but I'm this issue out of the backlog for now because it's unlikely to ever be prioritized.

[xwipeoutx]

Hi @jeremydmiller, thanks for that. All good just kicking it to the backlog - this was something that surprised me, but wasn't a hard blocker - I was just prototyping.

I ended up switching to using the EF Core integration, as we already had converters that aligned with our Json.NET configuration, so happy days here.