Fixes #156

Hello there ☺️

This PR is attempting to fix the crash/incompatibility with NativeAOT:

• Breaking change for IZLoggerFormatter which shouldn't be an issue. In all the call sites of FormatLogEntry, TEntry is always IZLoggerEntry and not an actual value type, so forcing IZLoggerEntry on the interface will avoid the crash at NativeAOT runtime Failed to create generic virtual method implementation (In general, it's better to avoid generic method with generic parameters in interfaces):

    public interface IZLoggerFormatter
    {
        bool WithLineBreak { get; }
  -      void FormatLogEntry<TEntry>(IBufferWriter<byte> writer, TEntry entry)
  -           where TEntry : IZLoggerEntry;
         void FormatLogEntry(IBufferWriter<byte> writer, IZLoggerEntry entry);
    }

• Add several [DynamicallyAccessedMembers(DynamicallyAccessedMemberTypes.PublicProperties)] to generics mostly to help with the usage of Json behind the scene.
• Added a few [UnconditionalSuppressMessage] for IL3050 and IL2026 due to the usage of several methods from JsonSerializer.Serialize which takes an object. The ones that are using JsonSerializerOptions should be fine as the user can set its own instance to SystemTextJsonZLoggerFormatter.JsonSerializerOptions and initialize it with a NativeAOT/Source generator version. There are other places where JsonSerializer.Serialize is used, but without the options. I'm not sure exactly if it will be a problem (I'm not using JsonSerializer for now). Ideally the same JsonSerializerOptions should be propagated to all these places, but it looks like JsonSerializer.Serialize in these cases might be only used for primitives.