Bump JasperFx 2.3.0: fix HTTP codegen-write service location (GH-2991)

[jeremydmiller]

Closes #2991. Supersedes #2992 (carries its reproduction, with @PerChr's authorship preserved).

Problem

With WolverineHttpOptions.ServiceProviderSource = FromHttpContextRequestServices, the runtime generated correct code (service-located deps from httpContext.RequestServices), but dotnet run -- codegen write generated different and wrong code: an opaque scoped lambda-factory dependency was service-located from an isolated serviceScope while a sibling DbContext used httpContext.RequestServices → two different scoped instances for one logical request.

Root cause + fix (JasperFx)

The CLI codegen paths (DynamicCodeBuilder) never applied the per-file TryReplaceServiceProvider/ReplaceServiceProvider step that the runtime DynamicTypeLoader does. Fixed in jasperfx#401 → JasperFx 2.3.0, including a new IServiceVariableSource.ResetServiceProvider() so the override is isolated per file on the CLI's shared source (otherwise it would leak httpContext.RequestServices into every following file). That PR carries the precise DynamicCodeBuilder regression test.

This PR

• Bumps JasperFx 2.2.7 → 2.3.0 (consumes the fix).
• Carries the Reproduction for "HTTP endpoints resolves services wrong in codegen, but works in tests" #2992 reproduction (EfCoreEndpoints /ef/servicelocation + http_handler_with_http_context_sourced_gets_the_same_service). Note: that test exercises the runtime path, which was always correct, so it passes pre- and post-fix — it documents the scenario and guards against a runtime regression; the codegen-write defect itself is guarded by the JasperFx test.

Verification

• Manually confirmed against this repro: regenerating WolverineWebApi with 2.3.0 via codegen write now resolves the opaque scoped service and the DbContext both from httpContext.RequestServices, with no leak of httpContext.RequestServices into non-HTTP MessageHandler files.
• using_efcore suite green on 2.3.0.

This bump changes codegen write/preview output for any consumer using a ServiceProviderSource override, so the full Wolverine CI here is the regression net — please watch it.

🤖 Generated with Claude Code