Release v22.49.1

Changed

• Chronicle packages now use 19.31.2, which rejects incompatible definition-derived guards in same-id batches. (part of #3005)

Fixed

• A command returning several EventForEventSourceId wrappers for one event source id no longer lets a guard derived from the command's own stream stand in for every event. Events written through a definition now reach the event sequence without a framework-derived scope, so Chronicle derives and validates each event's own guard; wrappers that override the definition with legacy routing and would need different guards for one id fail with IncompatibleConcurrencyScopesForEventSource before anything is enrolled or appended. A guard chosen with concurrency: true keeps its existing behavior. (part of #3005)