Tree crashes on mount with `Cannot read properties of null (reading 'scrollTo')` when a node title contains an autoFocus input

从 Tree.js 中的 Tree.scrollTo 开始，跟踪 issue 中描述的 NodeList ref 生命周期。先使用提供的 autoFocus 复现作为第一项检查，然后运行或添加提到的回归测试；当首次 mount 不再崩溃且测试覆盖该情况时，即可完成。

What happened

We render an inline editor (a text input with autoFocus) inside a tree node's title — a common inline-rename pattern. Mounting the tree crashes the entire React root:

TypeError: Cannot read properties of null (reading 'scrollTo')
    at Tree.scrollTo (Tree.js)

Because the error is thrown from React's focus event dispatch during the commit, it escapes any local error handling and unmounts the whole application root, not just the tree. We hit this in production via antd's Tree, which wraps this package; TreeSelect and Cascader share the same code path.

Reproduction

import Tree from '@rc-component/tree';

// Mounting this crashes the React root:
<Tree treeData={[{ key: 'a', title: <input autoFocus /> }]} />

1. Render a Tree where any node's title contains an element with autoFocus (or anything that focuses inside a row during the commit).
2. The input's focus bubbles to the tree container, the tree's focus activation runs scrollTo, and listRef.current is null at that moment → crash.

Why the ref is null

NodeList's useImperativeHandle has no dependency array, so on every commit the handle is detached during the mutation phase and re-attached in the layout phase. autoFocus focuses the input between those two, so the bubbled focus-activation dereferences a null listRef. First mount is the simplest trigger, but any re-render has the same window.

Versions

• @rc-component/tree 1.2.4 → 1.5.0 (current) — call sites unguarded in all
• React 19, reproduced in jsdom and real browsers

Fix

Proposed in #1067 — optional chaining on the two listRef.current.scrollTo call sites, plus a regression test that reproduces the crash on first mount.