Expand on Audited Members

[woksin]

Audit members are now also added as structured logging context to the Microsoft ILogger in message handler chain if any Audited members are present in the Chain AuditedMembers list or if the Aggregate Type has any Auditted members.

[woksin]

I would want to spend more time on writing tests, but I just added one very quick one to just see the compiled source code for message with Audit members. Here is the output of that test:

public class SomeMessageHandler797407002 : Wolverine.Runtime.Handlers.MessageHandler
    {
        private readonly Microsoft.Extensions.Logging.ILogger<CoreTests.Compilation.SomeMessage> _loggerForMessage;

        public SomeMessageHandler797407002(Microsoft.Extensions.Logging.ILogger<CoreTests.Compilation.SomeMessage> loggerForMessage)
        {
            _loggerForMessage = loggerForMessage;
        }



        public override System.Threading.Tasks.Task HandleAsync(Wolverine.Runtime.MessageContext context, System.Threading.CancellationToken cancellation)
        {
            var someMessageHandler = new CoreTests.Compilation.SomeMessageHandler();
            // The actual message body
            var someMessage = (CoreTests.Compilation.SomeMessage)context.Envelope.Message;

            // Application-specific Open Telemetry auditing
            System.Diagnostics.Activity.Current?.SetTag("id", someMessage.Id);
            System.Diagnostics.Activity.Current?.SetTag("some.string", someMessage.SomeString);
            var wolverineLoggingContext_loggingTools = new Wolverine.Logging.LoggingContext();
            wolverineLoggingContext_loggingTools.Add("TenantId", context.TenantId ?? "[NotSet]");
            // Adding audited members to log context
            wolverineLoggingContext_loggingTools.AddRange(("Id", someMessage.Id), ("SomeString", someMessage.SomeString));
            // Beginning logging scopes for new context
            using var disposable_b519d909_ba96_488d_9ed0_bb9c67c85771 = ((Microsoft.Extensions.Logging.ILogger)_loggerForMessage).BeginScope(wolverineLoggingContext_loggingTools);
            
            // The actual message execution
            someMessageHandler.Handle(someMessage, ((Microsoft.Extensions.Logging.ILogger)_loggerForMessage));

            return System.Threading.Tasks.Task.CompletedTask;
        }

    }

[woksin]

I see that for the AggregateHandler and Aggregate attributes I need to do something differently because it adds the logging middleware regardless of whether the logging context middleware is registered or not. Also there is probably some things that I'm missing or some other way to write this that makes it a bit better integrated