fix: revert Grid 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 currently 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 that in turn trigger some async renderers, 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.

This warning is particularly common in AutoGrid where a mix of sync (GridColumn) and async (Select) renderers is used. This PR reverts Grid to async rendering, which resolves the maximum depth warning and also improves performance. However, GridPro continues to use sync rendering because its web component currently requires the editor to render synchronously.

Fixes #255

Type of change

• Bugfix