Add excludeReplacedSegments param into table metadata API

/tables/{tableName}/metadata endpoint should take an additional parameter such as excludeReplacedSegments as found in getSegments in order to discern between reporting stats with consistent push accounted for or not.

Currently, the table returns TableMetadata with info such as diskSizeInBytes, numSegments and numRows approximately doubled when consistent push is in-place, and users who are unaware of the consistent push concept may incorrectly interpret the result, e.g. leading to provisioning 2x the storage by mistake.

This should be done in a backward compatible manner, with the default behavior being the current one if the additional param is not explicitly set.