Optimize controller UI for large cluster/tables

We have large tables that have over 220k and 370k offline segments, that we almost always timeout trying to open the offline table page, as it seems the page was trying to load all segment data on the page. It would be great if the UI can be redesigned or tweaked to not trying to load all those data on page load, to make UI more responsive.

Start with the controller UI's offline table page and trace how segment data is loaded when a table is opened. Reproduce the timeout with tables containing roughly 220k and 370k offline segments; done means the page no longer attempts to load all segment data at startup and remains responsive.

Written by the indexing model from the issue text.