support concurrent mode without triggering force update in provider

[dai-shi]

This is a new implementation with useReducer chat mode.

In the previous version, we triggered re-render in render in the provider component to support CM.
But, it gives us "Cannot update a component from inside the function body of a different component." warning. This is really hard one (related issue), because we rely on calculateChangedBit = 0 + subscription hack.

This version should work like useSubscription, and it will pass check 1-8 in https://github.com/dai-shi/will-this-react-global-state-work-in-concurrent-mode

This would affect to the performance, unfortunately. We will wait for useMutableSource for better implementation.

[dai-shi]

Hm, this implementation is somewhat similar to what I did in react-redux as an experiment. reduxjs/react-redux#1509
This still uses useRef, but we probably need it anyway with useTrackedState.

[dai-shi]

Okay, it looks like working. Good to go.