[facebook/react] [DevTools Bug]: react-hooks/set-state-in-effect misses setState in useEffect for anonymous component callbacks passed to HOFs

### ROOT CAUSE The issue arises because React DevTools relies on the component's hook to track state updates. When a `useEffect` in a child component uses a `setState` function passed from a parent (e.g., via a Higher-Order Component), the DevTools cannot associate the state update with the parent component's state, as the effect is not directly tied to the parent's hook. This happens because the DevTools tracks state updates based on the component and state variable, and the anonymous callback's origin is not properly recognized. ### CODE FIX ```javascript // In React's DevTools integration code (e.g., ReactFiberDevToolsHook) function markStateUpdate(parentComponent, statePath, newState) { // Track the state update even if called from a child component const origin = findParentComponentHook(parentComponent, statePath); if (origin) { updateDevToolsState(origin, newState); } else { // Fallback to the current component if origin is not found updateDevToolsState(currentComponent, newState); } } function findParentComponentHook(component, statePath) { // Traverse up the component tree to find the component that owns the state let parent = component; while (parent) { if (parent.statePath === statePath) { return parent; } parent = parent.parent; } return null; } ``` This fix ensures state updates from child components are properly attributed to the parent component by traversing the component tree to find the state's origin.