fix(events): remove async callbacks from code

[markov00]

Summary

Working at #1729 leads to an interesting issue regarding the asynchronous callback.
In particular, we were calling the onChartRendered and onProjectionAreaChanged callbacks in a new macro task thanks to a requestAnimationFrame.

The reasons to avoid this way of handling callbacks are:

• give the freedom to the user to choose how they want to execute/queue the task in their own environment
• events caused by mouse events are already async by nature
• those callbacks should be used only for small side effects, like triggering a focus, a slight change in the state (like disabling a loading spinner) etc the user should not attach long-running sync methods to these events.

This PR removes the use of RAF in favor of sync calls.

This solves a side issue in the composable story where the chart render-complete was not called correctly.

[nickofthyme]

Excellent!! Works great. Thanks for jumping on this so fast! Any idea why we wrapped those in a RAF?

[markov00]

Excellent!! Works great. Thanks for jumping on this so fast! Any idea why we wrapped those in a RAF?

If the user attaches very long sync function to a callback then the rendering phase of the event loop will start only after that sync function has completed, freezing the chart until the end of the callback.
Adding a RAF will push the callback in the queue and runs it after the rendering phase, reducing the freeze effect.
With that instead we want to push that decision to the users