feat: add support for constructor injection in middleware exception handling

[danielwinkler]

I posted the following question to discord but haven't gotten an answer yet

As I am not deep enough into the wolverine source generation, I can only offer a Claude generated solution for the problem; maybe it helps, otherwise please reject.

---

Hi,

I saw that there has been an IExceptionFilter equivalent introduced recently
#2410

From the documentation and also my experiments, I was unable to inject anything else than the excption into the handler

My goal would be to log the exception / stack trace, is there a way to achieve something like

public static class LoggingExceptionMiddleware
{
    public static ProblemDetails OnException(DomainException exception)
        => ApiExceptionMapper.CreateDomainExceptionProblemDetails(exception);

    // public static ProblemDetails OnException(DomainException exception, ILogger logger)
    // {
    //     // logger.LogWarning(exception, "HandleDomainException");
    //     return ApiExceptionMapper.CreateDomainExceptionProblemDetails(exception);
    // }
}

[jeremydmiller]

Thanks for this, @danielwinkler — closing as superseded by #3005, with you kept on as co-author there.

When I dug into the scenarios this PR targets, they already pass on main without the change: non-static/constructor-injected OnException middleware, ILogger constructor injection, static middleware with extra injected parameters, and a shared Before+OnException instance all work today (I added regression tests for each in #3005, including a stronger one asserting the same instance's state set in Before is visible in OnException). Because of that, the added BuildConstructorFrame() path (the "keep both in sync" duplication) isn't needed.

What surfaced instead is a genuine gap that neither main nor this PR addressed: a value returned from an OnException method was silently dropped rather than published as a cascading message — unlike a handler method's return value. #3005 fixes that (with a catch-block-safe cascade frame to avoid a codegen "Frame chain is being re-arranged" collision) and keeps all of the reproduced scenarios as regression coverage.

Really appreciate the push that led us here.

[danielwinkler]

Thanks for the feedback, really glad that I could contribute!