Feature: Support multiple table progress

[Xuanwo]

Address #8331

Summary

We are storing dal_metrics_read_bytes, dal_metrics_write_bytes in dal_metrics_write_bytes which is shared across the whole query. This doesn't make sense now because we could have multiple tables in the same query. Users should be able to know the metrics about different tables.

Thus, we should support multiple table progress reports.

Plan

• rename dal_metrics_read_bytes to table_data_read_bytes
• rename dal_metrics_write_bytes to table_data_write_bytes
• Add support for table_cache_{read/write}_bytes.
• Init the table data metrics while creating table instances instead of query start.

Other progress like scan_progress_read_rows and scan_progress_read_bytes should also be updated.

Tasks

• Implement single table support
• Implement multiple table support

[BohuTANG]

Can we get all-in-one metrics for a query? Like:

show processlist;

query_id| table_data_read_bytes: x | table_data_write_bytes: x | table_cache_read_bytes: x | table_cache_write_bytes: x

[Xuanwo]

Can we get all-in-one metrics for a query? Like:

We can get all tables attached to this query and then do a simple calculation.

[Xuanwo]

We will start by reusing current logic first: the global metrics for current query.