[UX] Remove association between an anomaly detector and a visualization

[xeniatup]

Is your feature request related to a problem?
As a user who want to manage information density on the dashboards I want to be able to remove some of the associations between anomaly detectors and visualizations.

UX Meta issue

What solution would you like?
opensearch-project/anomaly-detection#521
#400

Initial UX proposal on Anomaly Detection on Dashboards opensearch-project/OpenSearch-Dashboards#1798

User stories

1. User wants to be able to list all anomaly detectors associated with visualization
2. User wants to be able to list all visualizations associated with a given anomaly detector
3. User wants to be able to create/remove an association between a detector and a visualization.

For create association see #436

Unlink anomaly detector from a visualization

unlink-detector.mp4

Screen 1: User selects a visualization on a dashboard and selects "Anomaly detection" from the visualization context menu (OuiContextMenu):

Screen 2: User selects "Associated detectors" from the context menu:

Screen 3a: Selecting "Associated detectors" opens a flyout (OuiFlyout) with the list of all detectors (OuiBasicTable) associated with the visualization.

Screen 4: Selecting "Remove association" button icon from the "Actions" column opens a confirmation modal (OuiModal) dialog.

Screen 5: User selects "Remove association" and the modal dialog closes. User returns to the flyout. The success or fail message appears as a toast (OuiToast ). The list of anomaly detectors is reloaded and updated accordingly.

Screen 6: Detector name in the table points to the detector page in Anomaly Detection plugin.
User scrolls down the page to "Associated visualizations" table, listing all visualizations the detector is associated. If a visualization is incompatible with the plugin augmentation feature, a warning badge (OuiBadges) is displayed in the "Compatibility" column.

Screen 7: Selecting "Remove association" icon button from the "Actions" column triggers a confirmation modal (similar to screen 4).

Screen 8: User selects "Remove association" and returns to the detector page. A toast message appears, and the table is updated.

Additional states for "Associated detectors":

Screen 3b: Empty state for "Associated detectors" flyout (no anomaly detectors is associated with the visualization)

Screen 3c: When the limit of plugin objects per visualization is reached, a warning callout is added to the flyout, and the "Associate detector" button is disabled.

Screen 3d: Permissions error state. When user doesn't have required permissions to read the anomaly detectors associated with the visualization, the system shows "Associated detectors" flyout in empty state. A toast message opens with the security error. "Associate detector" button is hidden.

[xeniatup]

Done:
#400
opensearch-project/OpenSearch-Dashboards#2880
opensearch-project/alerting-dashboards-plugin#457