Release v1.12.2

Fixed

• An ExpandoObject that crosses a silo boundary keeps its shape. Before, every ExpandoObject nested inside it came back on the receiving silo as a Dictionary<string, object>, including a child in a collection or a nested object. Code that looks such a value up by its properties could no longer find them. In Chronicle, this made on-demand read models throw and then return nothing whenever the projection and its cached result ran on different silos (Cratis/Chronicle#4337). What is sent between silos is unchanged, so silos on either side of the upgrade keep working together during a rolling update.