[BUG] visAugmenter requiring savedObjectsManagement puts other features at jeopardy

[AMoo-Miki]

Describe the bug

A lot of visualizations indicate that they require bundles from visAugmenter who requires bundles from savedObjectsManagement and that requires the management plugin. If the management plugin is disabled everything falls apart.

Ideally, visAugmenter should gracefully degrade by not requiring savedObjectsManagement and checking if it is available before doing

uiActions.addTriggerAction(SAVED_OBJECT_DELETE_TRIGGER, savedObjectDeleteAction);

To Reproduce
Steps to reproduce the behavior:

1. Add management.enabled: false to the config
2. Restart and access OSD

Expected behavior
Everything should work

OpenSearch Version
Any

Dashboards Version
2.9.0

Additional context

#4642

[joshuarrrr]

Part of the underlying root cause is that savedObjectManagement takes dependencies in the wrong direction - it should provide a registration function instead of taking dependencies on visualize, dashboard, discover: #1836

[ashwin-pc]

This is actually a problem with the way UI Actions is built. The issue as seen in the screenshot is because the ui actions break the whole app when we try to register an action to a trigger that isnt registered. The saved object management plugin registers the trigger SAVED_OBJECT_DELETE_TRIGGER and the visAugmenter plugin binds to that trigger. Now when the saved object management plugin is disabled, the trigger is never registered and the visAugmenter plugin during startup throws an error when it tries to bind an action against a trigger that does not exist.