Release v19.90.0

Added

• New MaxConcurrentPartitions options for reactors and reducers in ChronicleOptions set how many partitions of one reactor or reducer the .NET client handles at the same time. The default is the processor count, capped at 8; 1 restores one-at-a-time handling. (part of #4664)

Changed

• The .NET client now handles different partitions of a reactor or reducer concurrently, while batches for one partition still run in order. Catch-up deliveries no longer time out while they wait behind other partitions in the client. Handlers for different partitions can run at the same time, so a handler that shares non-thread-safe state across partitions must protect it, or set MaxConcurrentPartitions to 1 to keep one-at-a-time handling. (#4664)