Include byte size estimates in the filter statistics

[isidentical]

Which issue does this PR close?

Closes #4374.

Rationale for this change

Just like num_rows, we now estimate the byte size for the output of a FilterExec operation.

What changes are included in this PR?

Estimation of total byte size through filter predictivity.

Are these changes tested?

Tests are included

Are there any user-facing changes?

No

[alamb]

LGTM -- thanks @isidentical

[ursabot]

Benchmark runs are scheduled for baseline = 323fbb4 and contender = 3bfdbaa. 3bfdbaa is a master commit associated with this PR. Results will be available as each benchmark for each run completes.
Conbench compare runs links:
[Skipped ⚠️ Benchmarking of arrow-datafusion-commits is not supported on ec2-t3-xlarge-us-east-2] ec2-t3-xlarge-us-east-2
[Skipped ⚠️ Benchmarking of arrow-datafusion-commits is not supported on test-mac-arm] test-mac-arm
[Skipped ⚠️ Benchmarking of arrow-datafusion-commits is not supported on ursa-i9-9960x] ursa-i9-9960x
[Skipped ⚠️ Benchmarking of arrow-datafusion-commits is not supported on ursa-thinkcentre-m75q] ursa-thinkcentre-m75q
Buildkite builds:
Supported benchmarks:
ec2-t3-xlarge-us-east-2: Supported benchmark langs: Python, R. Runs only benchmarks with cloud = True
test-mac-arm: Supported benchmark langs: C++, Python, R
ursa-i9-9960x: Supported benchmark langs: Python, R, JavaScript
ursa-thinkcentre-m75q: Supported benchmark langs: C++, Java