Release v16.35.1

Fixed

• Keyed child updates in hierarchical projections no longer re-resolve the child's creation event on every subsequent event of the same event source: when the event carries the child's key and the child is already projected under the document the resolved parent key identifies, its placement is resolved with a single sink lookup — eliminating the per-event FromParentHierarchy Warning flood and the redundant event-sequence lookups that preceded each warning (#3723)
• The creation-event rejection guard in FromParentHierarchy now logs at Debug when the current event is itself the earliest candidate creation event — the normal steady-state outcome; only a creation event strictly later than the current event is still rejected with a Warning, as the genuine infinite-cycle anomaly (#3723)
• A child projection event that does not carry the property configured as its parent key now fails with a descriptive MissingParentKeyForChildEvent — naming the projection, the children collection, the identified-by property, and the event type, sequence number and event source — instead of a bare ArgumentNullException (Parameter 'value') that left failed partitions without a usable message (#3725)