`AfterRenderImpl.addSequence` added the sequence straight to `sequences` without checking whether hooks were already running. If a view was change-detected from inside a render hook (for example, when a custom element connects to the DOM during a render phase), its `afterRenderEffect` sequence could be added mid-pass. The phase loop would then run its later phases in the current pass and skip the earlier ones, so `earlyRead` could run a tick after `write`. This also shifted the phase callback arguments and eventually caused `TypeError: fn is not a function` when the view was destroyed.

Defer these registrations to the next pass, like `register` already does for sequences registered outside a view.

Fixes angular#61715