Drop HttpChainDescriptor pipeline-introspection fields; bump JasperFx 2.8.0 + Marten 9.4.0 (#3008)

[jeremydmiller]

Closes #3008. Producer side of the JasperFx descriptor cleanup (#411).

Status check first

Nothing for #3008 had landed on main (the population code + helpers were intact, JasperFx still 2.4.1). #411 is now closed/shipped — but the property removal only exists in JasperFx 2.8.0, so the issue is still open and was newly unblocked, not closeable. The prescribed "bump JasperFx" therefore became a 2.4.1 → 2.8.0 jump coupled to the Marten family.

Coordinated dependency bump

HttpChainDescriptor.Middleware / ServiceDependencies / Postprocessors (and MiddlewareStepDescriptor) are removed only in JasperFx 2.8.0 (still present in 2.5.0 / 2.6.x). So:

• JasperFx family 2.4.1 → 2.8.0 (RuntimeCompiler stays on its 5.x line)
• Marten family 9.2.0 → 9.4.0 — Marten 9.4.0's JasperFx floor is 2.5.0 (vs 9.2.0's 2.2.0), keeping the compiled-against vs runtime gap to 2.8.0 as small as published Marten allows
• Weasel.* 9.0.1 → 9.0.2 — required by Marten 9.4.0
• Polecat stays 4.2.1 — floor 2.2.0, satisfied by 2.8.0

Code change

In HttpGraphUsageSource: stop populating the three fields and delete the now-dead describeFrames / readServiceDependencies helpers (plus the now-unused buildChainDescriptor services parameter and the JasperFx.CodeGeneration.Frames using). Per the issue, the CritterWatch Pipeline tab moves to the existing RequestHandlerSourceCode lazy fetch, which returns the actual compiled pipeline — no operator-facing information is lost. CascadingMessageTypes (added in 2.8.0) is unaffected.

Validation

• Full wolverine.slnx Release build clean (net9.0 + net10.0), 0 warnings / 0 errors — i.e. no test references the removed JasperFx members.
• CoreTests 1735, MartenTests 461, Wolverine.Http.Tests 777, PolecatTests 216 — all green against the live infra. This exercises JasperFx 2.8.0 codegen, Marten 9.4.0 event-sourcing, and Polecat-on-2.8.0 runtime.

Notes

• No dedicated test exists for HttpGraphUsageSource, and the descriptor fields are gone from the type, so there's nothing to assert-negative on the producer side.
• I did not bump the Wolverine package version — left for you as a release decision (the precedent Marten bump landed alongside a version bump in a release commit).
• Downstream CritterWatch follow-up (Pipeline-tab UI removal) is tracked separately per the issue.

🤖 Generated with Claude Code