Enhance TableSize API to return compressed size in deep store

[eaugene]

Carrying out this from: #10812 (review) .
It looks like a nice feature to have to see disk usage in the deep stores as well.

Creating this issue to further track discussions

I can work on this, please assign this to me. 😊

labels : feature

[eaugene]

@mayankshriv Getting the segment-level compressed info would consume a solid time when we try to get for every segment of the large table ( probably making a API caller timeout ) . Should we instead get this info when the segment is pushed to deepstore and persist in SegmentMetadata ?

[Jackie-Jiang]

@eaugene The compressed segment size should already been persisted within the segment ZK metadata under the key segment.size.in.bytes. See #8358 for more details