Description of problem:

The operation ID returned from the backend API failure is not displayed in the OCM UI error messages.

This issue occurs when the delete action for an OSD trial cluster fails due to a backend error. Although the operation ID is included in the API response, it is not shown in the UI.

Displaying the operation ID in such cases would be helpful for debugging and coordinating with the backend team, especially when the cause of the failure is not immediately clear.

Steps to Reproduce:

I don't have exact steps to reproduce the issue, as it occurs due to a backend error.
However, simulating an inline backend error response against the UI might help in reproducing the problem.

Request API : 
https://api.stage.openshift.com/api/clusters_mgmt/v1/clusters/2j6s35lq8b381jr5ocaj1rsaju1n3545 
Method : DELETE
Response from API

{
    "kind": "Error",
    "id": "403",
    "href": "/api/clusters_mgmt/v1/errors/403",
    "code": "CLUSTERS-MGMT-403",
    "reason": "Failed to delete cluster 2j6s35lq8b381jr5ocaj1rsaju1n3545: Forbidden access to delete resource",
    "operation_id": "80c6e02a-1144-49e7-a592-0ed86c4fb622",
    "timestamp": "2025-06-04T09:34:56.554588538Z"
} 

Actual results:

"operation ID" value is missing from error messages from OCM UI .
In this case, delete action on osd trial cluster failed due to backend API issue and operation id present in API response but the same is missing in OCM UI error message.

Expected results:
Add missing "operation ID" value from backend response in OCM UI error messages.