Make uiActions available via renderer handlers

[timroes]

As it came up in this comment we currently need to pass down uiActions through the whole plugin to get access to in an expression renderer (where it will most commonly needed in every renderer). Could we somehow give access to the executeTriggerActions function via the handlers passed to renderers?

This would prevent us from needing to use getterSetter in those places, since we need to register the renderer in the setup method (since that is where the expressions plugin exposes the registerRenderer function), and the executeTriggerActions is only available in the start phase. So we need to always work with the createGetterSetter approach. I think it would be benefitial for a lot of renderers, if we would just have access to executeTriggerActions via handlers.

cc @ppisljar @stacey-gammon

[elasticmachine]

Pinging @elastic/kibana-app-arch (Team:AppArch)

[lukeelmers]

This would prevent us from needing to use getterSetter in those places

Could createGetterSetter instead be replaced with core.getStartServices() so that we don't need to throw something else in the handlers? Somewhat related to #61106

[timroes]

Yes I wasn't aware of that method, I would say that's indeed the better solution (implemented in #61421). Closing this issue.