Release v19.60.0

Added

• Webhooks can opt in to receive every event in the generation they subscribed to, on live delivery, catch-up, replay and partition retries alike. Opt in with WithGenerationDelivery(EventGenerationDelivery.Pinned) on the .NET webhook builder, or set GenerationDelivery to Pinned when registering webhooks directly. The kernel records each subscribed event type's generation with the webhook and selects, decrypts and, when needed, migrates the event to that generation before posting it; the payload envelope is unchanged. Webhooks that do not opt in are unchanged. See webhooks (part of #4710)

Changed

• Registering an opted-in webhook fails, before anything is recorded, when it names an unregistered generation or two generations of the same event type, the same rule that applies to opted-in reactors, reducers and projections (part of #4710)
• When a pinned event cannot be released in its pinned generation, the webhook sends no request and fails the batch without acknowledging it, so it is retried instead of being skipped (part of #4710)