[Lens] Set up editor frame expression execution integration

[flash1293]

• Pulls in dependencies through old plugin and new plugin shim
• Executes them on changes
• Renders result into container

Reference: src/legacy/core_plugins/interpreter and implementation in POC (https://github.com/elastic/kibana/tree/feature-branch/viz-editor)

[elasticmachine]

Pinging @elastic/kibana-app

[flash1293]

Just synced with @ppisljar on this:

• This is a cross cutting concern and will be needed all over Kibana
• Because of this we are going to move this to the data plugin and just use it in Lens
• To get started we will implement a minimal version which will get extended with features (caching etc.) over time
• Usage in Lens will test the feature before introducing it in the current visualize editor

interface ExecutorOptions {
    domElement?: Element;
    // TBD
}

interface ExecutorResponse {
    // TBD
}

run(expression: string | AST, options?: ExecutorOptions) => Promise<ExecutorResponse>;

CC @wylieconlon @chrisdavies

[flash1293]

Synced with @timroes on this:
The run method proposed in the last comment is a convenience API on top of the stuff discussed in #25374 It can be implemented first to get Lens running, but should be marked as experimental as details around this may change.

[flash1293]

Closing this as the basic functionality is there