Currently we have the following metadata in the query response:

• numSegmentsQueried: number of segments queried by the broker
• numSegmentsProcessed: number of segments processed after the server-side segment pruning
• numSegmentsMatched: number of segments that has records matched
• numConsumingSegmentsQueried: number of consuming segments queried by the broker

We want to also add numConsumingSegmentsProcessed and numConsumingSegmentsMatched to the query response metadata.

Note: In the DataTable.MetadataKeys, we mistakenly use NUM_CONSUMING_SEGMENTS_PROCESSED to represent the numConsumingSegmentsQueried