Improve how we pass dependencies into components in TriggersActionsUI

[gmmorris]

Follow up from #78746

@YulNaumenko suggests we improve how we pass dependencies into components in TriggersActionsUI #78746 (review)

My proposal is to use kibanaReact and useKibana object for adding all common dependancies - this will allow us to remove a lot of repeating code that we path throught the components props. All the plugins have this Kibana context available. I'm not sure how much time it will take for refactoring this, maybe a follow up issue should be created. But we definitely should switch to kibanaReact.

[mikecote]

Is this a duplicate of #65146?

[elasticmachine]

Pinging @elastic/kibana-alerting-services (Team:Alerting Services)

[YulNaumenko]

Yeah, I forgot that I've already opened this issue a long time ago. But it seems to be more critical to fix it now, because our components props number are growing fast and could be replaces with kibanaReact. So we should consider a Higher priority on this issue

[mikecote]

Thanks @YulNaumenko! I went ahead and added the other issue (#65146) back into triage so it can be discussed at the next triage session. I will close this one as a duplicate 🙏