…riggered. Run the batch as a microtask at the end of the current task.

I hit a problem with the edge cases and out-of-order execution of updates. I need to use React batching of changes, which requires using only one micro task for all views, instead of a separate micro task for each view as it is now.

When react-easy-state changes are triggered from the main event loop,
they must run inside the main event loop, instead of being batched in
the microtask. Otherwise, the cursor will jump to the end of input
elements, since the change can't be tied back to the action
taken. React batches changes caused inside an event loop, so we can
rely on the normal React setState batching.

React automatically batches setState calls, but only inside its own
event handlers. If we know we've scheduled a batch update, we should
run the changes using batchedUpdates -- at the end of an event loop,
if we're in an event, or in the microtask if we're not.

The previous fix still had the input element problem in React
production builds. This way we guarantee updates will run in the way
React expects them to.

…er changes"

This reverts commit 6203429.

That change caused incorrect cursor movement in many more places, and
is not a correct fix to the original problem.