[UiActions] pass trigger into action execution context

[Dosant]

Summary

Partially addresses: #63854
This is a follow up on #71675 which takes a bit different (more strict) approach.

Reason why I didn't like #71675 is that it was super easy to not pass trigger into action handler.
I even missed some places in that pr.

This pr takes different approach:

We already have a separation between Action and ActionDefinition.
Those are used almost interchangeably in different places, which is confusing. The usage should be aligned in #74501:

1. Action should be used internally and should represent the object returned by uiActions service
2. ActionDefinition is a simple interface and should be used for registering an action in uiAction service.

With that:

As ActionDefinition should stay as simple and flexible as possible to provide the simplest api for defining and action, argument type of handlers do not required to specify trigger.
So when defining an action as ActionDefinition usage stays the same in simple cases:

class MyAction implements ActionDefinition<Context> {
....
execute(context: Context) {

}
....
}

But if need to access context, consumer could use type helper:

class MyAction implements ActionDefinition<Context> {
....
execute(context: ActionExecutionContext <Context>) {
  // to access the trigger:
  // console.log(context.trigger)
}
....
}

But in Action interface trigger is required now.
So if consumer uses action directly or defines an action using Action interface instead of ActionDefinition then:

action.exec({...context, trigger})

---

Action, ActionDefinition, createAction are used interchangeably and intersect with each other. These interface usage should be documented and aligned: #74501

[Dosant]

@elasticmachine merge upstream

[Dosant]

@elasticmachine merge upstream

[streamich]

Tested on Chrome, LGTM.

[Dosant]

@elasticmachine merge upstream

[elasticmachine]

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

[Dosant]

@elasticmachine merge upstream

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: 664ffcf

Build metrics

@kbn/optimizer bundle module count

id	value	diff	baseline
uiActions	32	+1	31

page load bundle size

id	value	diff	baseline
embeddable	428.6KB	+1.4KB	427.2KB
uiActions	213.6KB	+3.4KB	210.2KB
total		+4.8KB

History

• 💚 Build #67916 succeeded 0885335
• 💚 Build #67196 succeeded 0a3aed6
• 💔 Build #66879 failed bf563fa
• 💔 Build #66872 failed 5567d8e
• 💔 Build #66834 failed 2c9c359

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream