Add InvokeTracingMode.Full for full logging on InvokeAsync calls

[jeremydmiller]

Summary

Addresses the community request from PR #2349 with a proper opt-in approach.

• New enum: InvokeTracingMode with Lightweight (default) and Full values
• New property: WolverineOptions.InvokeTracing controls behavior
• New class: TracingExecutor — a separate IExecutor implementation that adds full structured logging to InvokeInlineAsync() (execution started, succeeded, failed, finished)
• No runtime overhead: The executor type is selected at build time based on InvokeTracing setting — no if/then branching in the hot path

Usage

using var host = await Host.CreateDefaultBuilder()
    .UseWolverine(opts =>
    {
        opts.InvokeTracing = InvokeTracingMode.Full;
    }).StartAsync();

When enabled, InvokeAsync() emits the same log messages (event IDs 102-105) that transport-received messages already produce — execution started/finished, message succeeded/failed.

Files changed

File	Change
WolverineOptions.cs	Added InvokeTracingMode enum and InvokeTracing property
TracingExecutor.cs	New IExecutor implementation with full logging
Executor.cs	Updated Build() methods to select TracingExecutor when Full
invoke_tracing_mode.cs	5 new tests (default setting, lightweight no logs, full logs on success/failure/finish)
logging.md	New "Full Tracing for InvokeAsync" section
tutorials/mediator.md	Added tracing note
guide/http/mediator.md	Added tracing note

Test plan

• 5 new invoke tracing tests pass
• CoreTests: 1214 passed, 0 failed
• HTTP tests: 553 passed, 0 failed

🤖 Generated with Claude Code