fix: revert useRenderer hook to async rendering

[vursen]

Description

Wrapping renderers in flushSync doesn't guarantee that the DOM will be updated synchronously. React may still defer it to a micro task if flushSync was called while rendering was already in progress, which is explained in the suppressed warning:

Warning: flushSync was called from inside a lifecycle method. React cannot flush when React is already rendering. Consider moving this call to a scheduler task or micro task.

When there are many deferred sync renderers (GridColumn) that in turn trigger some async renderers (Select), it can create race conditions that React misinterprets as a possible infinite loop:

Warning: Maximum update depth exceeded. This can happen when a component calls setState inside useEffect, but useEffect either doesn’t have a dependency array, or one of the dependencies changes on every render.

Since synchronous rendering isn't guaranteed, it pretty much defeats the purpose of using flushSync in renderers. I think we should rather try to improve web components to support async renderers.

Fixes #255

Type of change

• Bugfix

[vursen]

Closing in favor of #273