Profiler should only report stateful hooks that change between renders

[bvaughn]

Related to #24182

The Profiler has an advanced feature that shows why a component re-rendered. In the case of props and (class) state, it shows the names of props/state values that changed between renders. For hooks, DevTools tries to detect which ones may been related to the update by comparing prev/next internal hook structures.

My initial implementation tried to detect all changed hooks. In hindsight this is confusing, because only stateful hooks (e.g. useState, useReducer, and useSyncExternalStore) can schedule an update. (Other types of hooks can change between renders, but in a reactive way.) This PR changes the behavior to only report hooks that scheduled the update.

---

cc @acdlite, @lunaruan

This coupling between DevTools and React is pretty flaky and could break in future updates. IMO it seems better if React itself provided some kind of enum to identify the hook type, rather than requiring DevTools to do duck typing. Either that, or React could provide some way for DevTools to query the hook type via the renderer interface.

If React were to add support for this, DevTools could still fall back to the duck typing check for older versions.

(We might want to have a larger discussion here at some point soon?)

[bvaughn]

These fields haven't changed in two years (#17560 was the most recent time) so they seem pretty stable. On the other hand, lanes fields are pretty tied to the current implementation.

If we refactor useState in the future to not be built on top of useReducer then this could change.

[bvaughn]

These fields mirror the public API and so they seem stable-ish?

[bvaughn]

Note that I'm intentionally not including useMutableSource since it's short lived.

[bvaughn]

I pulled these bits of the snapshot data inline so it's more clear what they're testing.

Running this same test on main branch shows a lot of "failures" (e.g. effect/callback hooks being reported).