[expressions] couple to UI Actions

[ppisljar]

Currently expression renderer can use handler.emit to emit pretty much anything but it can't know what will actually be handled by the application consuming the expressions. Application could decide to do anything with the value, but most applications today handle the value to UIActions plugin.

To standardize the way expression events work we should couple expressions with UIActions:

• add optional dependency on UIActions to expressions plugin
• add optional parameter getExtraActionContext: () => Context to ExpressionRenderHandlerParams
• remove hasCompatibleActions from ExpressionRenderHandlerParams
• add preventDefault: () => void to ExpressionRendererEvent
• expression renderer event handler should emit the value, check if preventDefault was called and if not call uiActions?.executeTriggerActions(name, { …context, ...getExtraActionContext() });
  note: above should only happen when rendering with interactions enabled
• update consumers to either call .preventDefault() on event and manually handle it, or even better remove the manual handling in favor of internal handling with uiActions
  • lens should not prevent default but let expressions emit uiAction, lens should still call correct method on this.input (still needs subscription to events$)
  • visualize should prevent default only for bounds event, for all other events it should not do anything
  • canvas currently doesn't subscribe to events$. It probably shouldn't and should let expressions call uiActions even when it moves to the new filtering approach.

[elasticmachine]

Pinging @elastic/kibana-app-services (Team:AppServices)

[elasticmachine]

Pinging @elastic/kibana-visualizations @elastic/kibana-visualizations-external (Team:Visualizations)