Release v19.62.4

Changed

• The seeding documentation now states the scope of global seeds:
  • A global seed reaches every namespace of the event store, including ones created later, once.
  • Opening a store for a new namespace creates it, and the kernel then applies the stored global seeds. This usually happens before the application's first write, but the order is not guaranteed.
  • Development or sample data belongs in ForNamespace(...).
  • Removing a global seed from code does not remove the stored entry yet (part of #4869)

Fixed

• The .NET client sends the global event seeds discovered from ICanSeedEvents once per event store on each connection, instead of again for every namespace store it opens. Seeds added through ForNamespace(...) and seeds queued by hand are still sent every time (part of #4869)