Release v19.77.3

Changed

• Repeated strongly consistent reads of the same key no longer reuse earlier work. Each read costs roughly what a first read costs, and that cost grows with the number of events for the key. Prefer a materialized projection for long histories that are read often, or that a reactor reads on every event. (part of #4844)

Fixed

• Strongly consistent per-key projection reads (passive projections, stream-scoped reads, reads with the * key and session reads) now fold the key's events from the start on every read. Redactions, revisions and the erasure of personal data joined from another subject show up immediately. Before, a warm read kept returning the old content until the grain was deactivated. (#4844)