Use Actions / Triggers for Creating Panels

[cqliu1]

Describe the feature:

We should register a uiActions trigger to allow other plugins to register creation links for Dashboard.

Describe a specific use case for the feature:

The editor menu that allows new panels to be created is currently populated with visualizations and embeddables by the Dashboard. Instead of Dashboard generating these menu items, we should have the apps register actions for creating their corresponding embeddables.

Registering the menu options as uiActions would give us better control of the ordering and grouping in the menu while also reducing the dependencies in Dashboard since Dashboard is pulling in the vis type registry and embeddable factory registry to populate the menu.

This would also make it easy for Canvas and other apps to use the same actions to handle embedding visualizations.

Here's a example snippet of how the uiActions can be registered:

// In dashboard:
<button onClick={plugins.uiActions.getTrigger('ALL_EDITORS_CLICK').exec({...})}>All editors</button>

// Other plugins, say Lens:
plugins.uiActions.createAction({
  id: 'GO_TO_LENS_EDITOR',
  order: 1000000,
getHref: () => '',
  execute: async () => {
    // go to lens
  },
});

plugins.uiActions.attachTriggerAction('ALL_EDITORS_CLICK', 'GO_TO_LENS_EDITOR');
//In Canvas:

<button onClick={plugins.uiActions.getTrigger('ALL_EDITORS_CLICK_CANVAS').exec({...})}>All editors</button>
plugins.uiActions.attachTriggerAction('ALL_EDITORS_CLICK_CANVAS', 'GO_TO_LENS_EDITOR');
or

<button onClick={plugins.uiActions.getTrigger('ALL_EDITORS_CLICK').exec({...})}>All editors canvas</button>

It would be nice to have the vis type registry and embeddable factory registry automatically register uiActions so plugin developers can get uiActions out of the box when registering a new vis type or embeddable.

[elasticmachine]

Pinging @elastic/kibana-presentation (Team:Presentation)

[cqliu1]

Closing because this is done. There is now an ADD_PANEL_TRIGGER trigger.