Add bytes subscription

* perf(useResizeColumns): optimize dispatch count for #3165

* console log demo

* Revert "console log demo"

37a69f5

* test(useResizeColumns): update tests

Co-authored-by: Joseph Schenck <joseph@josephschenck.com>

Change `isAllRowsExpanded` from `instance` to recalculating it by using `state` because `isAllRowsExpanded` from `instance` is toggled twice on React.StrictMode.

Ref. #3061

Co-authored-by: Spencer Collins <spencer.collins@spreetail.com>

Add the computed depth to leaf rows returned from groupUpRecursively

fixes #3631

Other plugin pages explicitly mention this flag (e.g. useExpanded), but useGroupBy didn't — added it in!

…4207)

React 18 removed some logic from `useReducer()` where a dispatch would eagerly call reducers to recompute the state so now reducers will be called after render. This poses a problem for `useTable()` because during render it mutates the `instance` by spreading in `props` and does not expect this to happen before reducer execution. We were passing a `pageCount: undefined` prop to `useTable()` and by the time the reducer executes `instance.pageCount` is been overwritten, causing a bug in our app. In the Codesandbox reproduction you can see that hitting the "next" button will not work. I understand that our abstraction around `useTable()` probably shouldn't be passing this prop when `undefined` but the behavior change was unexpected and I wonder if it breaks any other assumptions that this library makes. The fix I made here is to just replace `useReducer` with `useState`, which still has the eager bailout check.

React PR in question: facebook/react#22445
Codesandbox repro: https://codesandbox.io/s/cool-edison-45tkqx?file=/src/App.js:1331-1358