Release v3.14.0

A new reactor catches up from the very beginning of the event sequence, and once_only does not stop that. A reactor whose handlers cause side effects can now opt out of history with start_at_tail: true.

Added

• start_at_tail: true option on use Chronicle.Reactors.Reactor. The first time Chronicle sees the reactor, it begins at the tail of the event sequence and observes only what is appended afterwards. A reactor that already has a position keeps it. See https://github.com/Cratis/Chronicle.Elixir/blob/main/Documentation/reactors.md#starting-at-the-tail. (part of Cratis/Direct#1875)

Changed

• Requires cratis_chronicle_contracts 19.70 and a Chronicle server of 19.70.0 or later. Upgrade the server first: an older server ignores the option and the reactor catches up from the beginning.