Architectural Flaw: Silent Failures on Destructive Mutations in Storage Analytics

### Bug Report: Silent Failures on Deletion Mutations **Summary** During a deep architecture audit of TanStack React Query implementations within the Studio, I identified several destructive mutations (Deletes) that are actively swallowing errors via empty `onError: () => {}` closures. If a deletion fails on the backend (e.g., due to network disruption, RLS, or timeouts), the UI fails silently. No error toast is rendered, and the user is left with a false sense of success, leading to critical state desync between the client and the database. **Affected Files & Mutations:** All located within the `AnalyticsBuckets` module: 1. `useIcebergNamespaceTableDeleteMutation` in `TableRowComponent.tsx` (L83) 2. `useDeletePublicationMutation` in `useAnalyticsBucketAssociatedEntities.tsx` (L109) 3. `useDeleteDestinationPipelineMutation` in `useAnalyticsBucketAssociatedEntities.tsx` (L111) **Steps to Reproduce (Conceptual)** 1. Navigate to the Analytics Buckets / Iceberg Namespace UI. 2. Trigger a deletion for a Namespace Table or Pipeline. 3. Simulate a network failure or trigger a 500 from the API. 4. Observe that the UI does not alert the user; the error is caught and swallowed by the empty callback. **Expected Behavior** Destructive mutations must never swallow errors. They should pipe the error to the global `toast.error()` handler so the user is aware the deletion failed and can take remedial action. **Suggested Fix** Remove the empty `onError` closures and replace them with standard `toast.error(error.message)` notifications, or allow the mutation to fall back to the default global error boundary. I will be opening a PR shortly to patch these closures.