Release v19.31.2

Fixed

• A .NET batch appended through event source definitions no longer guards only the first event of an event source id. Every event sharing the id is resolved: equivalent guards share one scope, an event with no guard never hides a later guarded one, and explicit caller scopes still take precedence. (part of #4545)
• A batch whose events need different guards for the same event source id (for example different stream ids, or different definitions) now throws IncompatibleConcurrencyScopesForEventSource before anything is appended, instead of silently leaving later events unguarded. Pass an explicit scope that suits every event, or append in separate batches. See https://github.com/Cratis/Chronicle/blob/main/Documentation/clients/dotnet/event-sources.md (part of #4545)