Check scoped constraints in kernel-free event scenarios

[woksin]

Added

• EventScenario in @cratis/chronicle/testing now checks scoped constraints kernel-free: single-string property constraints, single-event-type constraints and two-type removal cycles in every scope combination, with ownership, replacement, removal, cycle release and atomic batch rollback applied per scope, as captured from the Chronicle kernel. (part of Add EventScenario and ReactorScenario to @cratis/chronicle/testing #129)
• EventScenario.append now accepts the sourceType, streamType and streamId routing options. (part of Add EventScenario and ReactorScenario to @cratis/chronicle/testing #129)

Changed

• EventScenario.append and appendMany now accept empty route strings, which resolve to Default, All and Default like the kernel; an empty per-entry route overrides the shared route. Previously they were rejected. (part of Add EventScenario and ReactorScenario to @cratis/chronicle/testing #129)

[woksin]

Reviewer notes (not release notes):

• Increment 5.5 of Add EventScenario and ReactorScenario to @cratis/chronicle/testing #129 (plan: scoped constraints + single-append routing). Unblocked by Testing: in-memory constraint storage drops constraint scopes Chronicle#4361, fixed in Cratis.Chronicle.Testing 19.26.2 (pinned since Update Cratis dependencies to Chronicle 19.26.2 #174).
• Evidence: new projection-oracle fixtures capture 592 operations from the packaged 19.26.2 kernel, using the actual TypeScript protobuf encoding and asserting the installed kernel definitions (scope, removal, casing, property order).
• Open API decision (not in this PR): scenario builders stay default-route-only; a forEventSource(id, options?: AppendOptions) overload is proposed for a follow-up.
• Reviews: full cross-provider review workflow; the one confirmed finding (legacy-decorator spec misnamed, so it ran with standard decorators) fixed in 34500e8 and the spec now passes under legacy decorators.