intent: fix the ResilienceBpmnTest SEND fixture self-loop, refuse next: <self> at parse, and correct the resilience-wiring text (#7226)

[NicoleNG18]

Three leftovers from #7165 (#7056, step resilience on a notify: service task).

1. The SEND_YAML fixture was a self-loop

ResilienceBpmnTest built the send fixture with two .replace calls: the first inserted the notifyOwner send step carrying onError: recordFailure, next: done; the second then replaced every onError: recordFailure, next: done with ... next: notifyOwner - rewriting the just-inserted send too, so notifyOwner got next: notifyOwner and done was unreachable. The tests passed only because the parser checks that next: names an existing step.

• The second replace now targets provisionApp uniquely (its PT1M cycle), so the chain is provisionApp -> notifyOwner -> done. Two assertFlow assertions pin the corrected topology so the loop can't come back silently.
• aSendWithoutResilienceKeysEmitsNoCycle also carried a dead first .replace("... onError: notifyOwner, ", "") - that text never occurs - now deleted.

2. next: <self> is now refused at parse

A step whose next names itself was accepted with no diagnostic (it is an existing step), and a generated .bpmn with a self-targeting sequence flow spins. IntentParser now refuses it with a message naming the step; StepResilienceIntentTest.aNextTargetingItselfIsRejected covers it. This silent acceptance is exactly what hid the fixture bug, so the guard and the fixture fix are one change.

3. The resilience-wiring text was stale in two places

engine-intent/CLAUDE.md and the javadoc of ResilientClassDelegateFactory described the wiring as config.setActivityBehaviorFactory(new DefaultActivityBehaviorFactory(...)); production (BpmFlowableConfig) wires new ResilientActivityBehaviorFactory(new ResilientClassDelegateFactory()) - the class #7165 added. Both corrected.

Verification

• mvn formatter:validate after wiping the formatter cache - BUILD SUCCESS.
• engine-intent unit suite - green (1188 tests, incl. the fixed ResilienceBpmnTest and the new StepResilienceIntentTest case).
• IntentEngineIT - green (74/74), confirming valid intents still parse and generate (the new guard refuses only a genuine self-loop).
• engine-bpm-flowable change is javadoc-only and compiles clean.

A stale-state core-initializers flake appeared mid-run (expected: <CREATE> but was: <UPDATE> on leftover H2 state); it passed 9/9 on a clean run and is upstream of and unrelated to this change.

Fixes #7226