Controller endpoint to surface exceptions per table

1. we should add this to controller end point as well and display in the UI
2. have something stored in ZK for errors for each table.
3. we can limit the size to few kbs
4. capture segment flush, consumption, API errors etc.

Start by tracing the controller endpoint and the UI path for table-level status, then review how errors are currently handled and whether ZooKeeper is used for related metadata. Define the storage size limit and the error categories to capture, including segment flush, consumption, and API errors. Done means these per-table exceptions are stored and surfaced through the controller and UI.

Written by the indexing model from the issue text.