[Canvas] Replace custom way of rendering of expression functions with expressions' one.

[Kuznietsov]

Introduction

While implementing the solutions for issues [Canvas] Remove filters and [Canvas][meta] Unify Expression Renderers and Deprecate flot, I've faced a couple of problems. The root of problems is the way of rendering expressions in Canvas.

---

Renderers, which are rendered in Canvas, are disconnected from the infrastructure of the Expressions. The biggest problem is custom handlers, which don't have a connection to the handlers, provided by Expressions. The answers to the question "Why do we need it?" you can find in the linked issues, which I've mentioned below.

---

These are problems, which are blocking further development:

• Need to support native expressions events, like applyFilterValue. [Canvas] Add support of native event handlers from expressions in renderers at Canvas. #122085
• Need to have access to variables, updateVariables, or uiState, which are available at native handlers of expressions. [Canvas] Support of uiState functionality at renderers in Canvas. #122108

Proposition

The idea of fast movement to the native expression renderer wrapper is to:

1. Replace element wrapper with ReactExpressionRenderer or add own wrapper around expressions.loader.
2. To save the previous behavior with custom handlers, as an additional way of working with existing logic, we can pass our own event as an onEvent prop of ReactExpressionRenderer.

cc @crob611, @ppisljar.

---

Issues, caused by the migration to expressions.ReactExpressionRenderer and which should be solved in the prior PRs

While implementing the PR, it has been raised couple of errors, which highlighted the conceptual issues, need to be fixed. They are described at the issue and should be solved at the prior PRs to the one with a migration.

[elasticmachine]

Pinging @elastic/kibana-presentation (Team:Presentation)