Remove circular dependency between uiActions & data/embeddable plugins

[smith]

The uiActions plugin imports types from the data and embeddable plugins:

kibana/src/plugins/ui_actions/public/types.ts

Lines 30 to 31 in 2c1bc50

	import type { RangeSelectContext, ValueClickContext } from '../../embeddable/public';
	import type { ApplyGlobalFilterActionContext } from '../../data/public';

These plugins have uiActions as a dependency, so there's a circular dependency here.

uiActions does not declare data or embeddables as dependencies in its kibana.json.

[elasticmachine]

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

[lukeelmers]

Plan here is to use the declare module pattern so that embeddables/data can augment the existing TriggerContextMapping instead of having their types directly imported.

While we want to stay away from this pattern in general, we decided it's okay in this case because a) It's the quickest way to unblock progress on folks moving to TS project refs; and b) We are already using this pattern for ActionContextMapping so it makes sense that we would go in and refactor everything at once in the future.

I'll have a PR up for this in a bit.

[lukeelmers]

We're getting close on finishing this one. PR is up here: #82791