Release v19.41.0

Added

• .NET reactors and reducers can opt in to receive every event in the generation they handle, on live delivery, catch-up, replay and partition retries alike. Set ChronicleOptions.EventGenerationDelivery to EventGenerationDelivery.Pinned; the kernel then selects, decrypts and, when needed, migrates the event to that generation. Without the option, delivery is unchanged. See event type migrations (part of #4710)
• The event context carries AppendedGeneration, the generation the event was originally appended in (part of #4710)

Changed

• Registering a pinned reactor or reducer fails when it handles a generation that is not registered for the event type, or two generations of the same event type (part of #4710)
• With SQL storage, revising an event now records the revised generation, so pinned consumers receive the revision. Revisions made before this release cannot be told apart from the original content (part of #4710)