[Security Solution] Show more alert action error info in error toasts (#269592)

## Summary

Addresses #269533.

When a user without sufficient index write access performs alert actions
in Security Solution, the error toast appeared with a blank body instead
of the actual reason from Elasticsearch.

### Cause

Several hooks called `addError(error.message, { title })`, passing a
plain string instead of the error object. `useAppToasts.addError` runs
its input through `errorToErrorStackAdapter`, which unpacks a Kibana
`HttpFetchError` (including the nested Elasticsearch reason string) only
when given the full error object. Passing `error.message` bypasses that
logic, leaving the toast body blank on permission errors.

### Fix

Pass `error` directly to `addError` in the following hooks:

- `useSetAlertAssignees` (`use_set_alert_assignees.tsx`) -- assign alert
- `useSetAlertTags` (`use_set_alert_tags.tsx`) -- bulk tag update
- `onAlertStatusUpdateFailure` in `useBulkActionItems`,
`useAlertActions`, and `useGroupTakeActionItems` -- open / close /
acknowledge
- `useCasesFromAlerts` (`use_cases_from_alerts.tsx`) -- cases fetch on
flyout open (fires automatically; users without Cases read access would
have seen a blank toast on every flyout open)

## Steps to reproduce

1. Create a role with `view_index_metadata`, `write`, and `manage` on
`.alerts-security.alerts-{space}`, but without `create_doc` / `index` /
`all`.
2. Log in as a user assigned that role and navigate to Security ->
Alerts.
3. Attempt any of the following:
   - Assign an alert to a user
   - Add or remove a tag via bulk actions
   - Change workflow status (open / close / acknowledge)
   - Open an alert flyout (if the user also lacks Cases read access)
4. Observe the error toast: the body is blank even though the browser
console shows a detailed authorization error.

**Expected:** the toast body shows the Elasticsearch authorization
reason (e.g. "action [indices:data/write/bulk[s]] is unauthorized ...").

Example:
<kbd>
<img width="655" height="599" alt="Screenshot 2026-05-15 at 4 42 24 PM"
src="https://github.com/user-attachments/assets/08fa0524-62f8-41e7-980b-25bbd1e49960"
/>

</kbd>
<kbd>
<img width="857" height="859" alt="Screenshot 2026-05-15 at 4 42 33 PM"
src="https://github.com/user-attachments/assets/d95635c5-f55d-44a7-8509-bb5a0960a74f"
/>

</kbd>

**Actual (before fix):** the toast body is blank.
Example:
<kbd>
<img width="372" height="205" alt="Screenshot 2026-05-15 at 4 44 53 PM"
src="https://github.com/user-attachments/assets/95ba3628-78a8-424c-9af4-0f61e9a2330e"
/>

</kbd>
<kbd>
<img width="857" height="859" alt="Screenshot 2026-05-15 at 4 44 34 PM"
src="https://github.com/user-attachments/assets/74f0e932-92a0-4188-9a43-e69ed28636bb"
/>

</kbd>

## Release note

Error toasts for failed alert actions (assign, tag, open, close,
acknowledge) now show the full error message from Elasticsearch instead
of a blank body.

---------

Co-authored-by: Cursor <cursoragent@cursor.com>
(cherry picked from commit cbabddd)

Author: rylnd

x-pack/solutions/security/plugins/security_solution/public/common/components/toolbar/bulk_actions/use_bulk_action_items.tsx

@@ -94,7 +94,7 @@ export const useBulkActionItems = ({
         case 'acknowledged':
           title = i18n.ACKNOWLEDGED_ALERT_FAILED_TOAST;
       }
-      addError(error.message, { title });
+      addError(error, { title });
       if (onUpdateFailure) {
         onUpdateFailure(newStatus, error);
       }

x-pack/solutions/security/plugins/security_solution/public/common/components/toolbar/bulk_actions/use_set_alert_assignees.tsx

@@ -40,8 +40,8 @@ export const useSetAlertAssignees = (): ReturnSetAlertAssignees => {
   );
 
   const onUpdateFailure = useCallback(
-    (error: Error) => {
-      addError(error.message, { title: i18n.UPDATE_ALERT_ASSIGNEES_FAILURE });
+    (error: unknown) => {
+      addError(error, { title: i18n.UPDATE_ALERT_ASSIGNEES_FAILURE });
     },
     [addError]
   );

x-pack/solutions/security/plugins/security_solution/public/common/components/toolbar/bulk_actions/use_set_alert_tags.tsx

@@ -41,8 +41,8 @@ export const useSetAlertTags = (): ReturnSetAlertTags => {
   );
 
   const onUpdateFailure = useCallback(
-    (error: Error) => {
-      addError(error.message, { title: i18n.UPDATE_ALERT_TAGS_FAILURE });
+    (error: unknown) => {
+      addError(error, { title: i18n.UPDATE_ALERT_TAGS_FAILURE });
     },
     [addError]
   );

x-pack/solutions/security/plugins/security_solution/public/detections/containers/detection_engine/alerts/use_cases_from_alerts.tsx

@@ -34,7 +34,7 @@ export const useCasesFromAlerts = ({ alertId }: { alertId: string }): CasesFromA
           setCases(casesResponse);
         }
       } catch (error) {
-        addError(error.message, { title: CASES_FROM_ALERTS_FAILURE });
+        addError(error, { title: CASES_FROM_ALERTS_FAILURE });
       }
       if (isMounted) {
         setLoading(false);

x-pack/solutions/security/plugins/security_solution/public/detections/hooks/alerts_table/use_group_take_action_items.tsx

@@ -134,7 +134,7 @@ export const useGroupTakeActionsItems = ({
         case 'acknowledged':
           title = i18n.ACKNOWLEDGED_ALERT_FAILED_TOAST;
       }
-      addError(error.message, { title });
+      addError(error, { title });
       refetchQuery();
     },
     [addError, refetchQuery]

x-pack/solutions/security/plugins/security_solution/public/detections/hooks/trigger_actions_alert_table/use_alert_actions.tsx

@@ -90,7 +90,7 @@ export const useBulkAlertActionItems = ({
         case 'acknowledged':
           title = i18n.ACKNOWLEDGED_ALERT_FAILED_TOAST;
       }
-      addError(error.message, { title });
+      addError(error, { title });
     },
     [addError]
   );