fix: change WithStepContext to only fire for steps with state name, no fallback to bare name

[kristina-solovyova]

Note

Medium Risk
Changes when the optional WithStepContext hook runs; integrations that relied on display-name fallback for stateless steps may see different context propagation in nested flows.

Overview
WithStepContext is now called only when a step has a non-empty step-state name from GetStepStateName(). The engine no longer falls back to the step’s display Name when building per-step context.

Stateless steps (including nested children inside a grouped step with no State) keep the context they already inherited—typically the parent stated step’s context—instead of being re-scoped under their bare display names. Comments in step_engine.go document this contract.

Adds TestWithStepContextOnlyForStatedSteps, which asserts WithStepContext runs for stated leaf and group steps ("leaf", "group") but not for stateless children (child1, child2).

^{Reviewed by Cursor Bugbot for commit efcf24a. Bugbot is set up for automated code reviews on this repo. Configure here.}

[kristina-solovyova]

• fix: change WithStepContext to only fire for steps with state name, no fallback to bare name #24 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.