tree: Fix bug with updating node parentage in sequence composition

[alex-pardes]

Description

Fixed a bug where sequence field failed to call onMoveIn in some cases when moving a node changeset during composition. This would lead to the composed changeset having incorrect node ancestry information, which could cause problems during other operations.

[github-actions]

Hi! Thank you for opening this PR. Want me to review it?

Based on the diff (7 lines, 2 files), I've queued these reviewers:

• Correctness — logic errors, race conditions, lifecycle issues
• Security — vulnerabilities, secret exposure, injection
• API Compatibility — breaking changes, release tags, type design
• Performance — algorithmic regressions, memory leaks
• Testing — coverage gaps, hollow tests

How this works

• Adjust the reviewer set by ticking/unticking boxes above. Reviewer toggles alone don't trigger anything.

• Tick Start review below to dispatch the review fleet.

• After review finishes, tick Start review again to request another run — it auto-resets after each dispatch.

• This comment updates as new commits land; your reviewer selections are preserved.

• Start review

[Copilot]

Pull request overview

Fixes sequence-field composition so that when composing move-related node changes (modifyAfter), the cross-field manager is notified via onMoveIn, preventing incorrect node ancestry/parentage in the composed changeset.

Changes:

• Removes onMoveIn invocation from ComposeQueue.dequeueBase.
• Invokes moveEffects.onMoveIn(...) when modifyAfter is retrieved in getModifyAfter, ensuring it also runs in cases like dequeueBoth.