fix(tree): trigger re-render when filter and onChange in Tree component

[kaylaa0]

Defect Fixes:

Fix #8381

Issue:

When the Tree component is configured with both the filter={true} prop and an onToggle callback, updates made to the tree nodes (e.g., changes to their expanded/collapsed state or content) are not reflected in the immediately subsequent render. The correct state only appears in the render cycle following that.

Solution:

1. Introduced a new internal state variable, forceRender.
2. The value of forceRender is toggled (set to its negative/opposite boolean value) whenever the tree's filter criteria change.
3. This state change forces the component to re-render, ensuring the latest node data is displayed immediately.

Result / Testing:

• Changes to the tree nodes' state (e.g., toggling a node) now render correctly and immediately in the same render cycle.

test_case.mp4

All specified cases were tested and are confirmed to be working correctly.