Release v19.24.0

The Workbench landing page works again, and the dashboards now follow the overview of the CLI workbench (see #3731).

Added

• The namespace dashboard - the page an event store opens on - is laid out like the CLI workbench overview: a server health rail (connection, version, CPU and memory, the store, namespace and tail sequence number, and the event types, projections, read models and namespaces in the catalog), observer, failure, recommendation and job tiles, event throughput over the last hour, day or week, observers over time, the top event types, a list of what needs attention and the jobs that are running.
• The event store dashboard adds the same figures up across its namespaces and lists every namespace with its events, observers, lag, failed partitions, recommendations and jobs, each leading to its own dashboard.
• Every tile and list entry leads to the page where the figure can be acted on.

Fixed

• The Workbench landing page no longer crashes to a blank screen while the key figures of an event store are loading, and the event stores are laid out across the width of the window.
• Event statistics now update as events are appended. Observers of all event types, such as the statistics, received nothing live and only moved forward when the server restarted.
• Event statistics now count each event type and namespace separately instead of folding every event into a single type in a single namespace.
• An event store created while the server is running now gets the kernel's own projections, such as the event statistics, straight away instead of after the next restart.
• The kernel's own projections now write to the storage the kernel runs on. On SQL storage they tried to use MongoDB and failed every event.