Build physical filter eagerly while constructing ParquetExec operator

We should avoid leaking logical expression to physical operators.

https://github.com/apache/arrow-datafusion/blob/master/datafusion/src/physical_optimizer/pruning.rs#L93-L101

https://github.com/apache/arrow-datafusion/blob/master/datafusion/src/physical_plan/file_format/parquet.rs#L77-L86

Read datafusion/src/physical_optimizer/pruning.rs around lines 93-101 and datafusion/src/physical_plan/file_format/parquet.rs around lines 77-86. Trace how ParquetExec is constructed and verify that physical filter construction happens during operator construction without passing the logical expression into physical operators; run the relevant existing test suite to confirm behavior is unchanged.

Written by the indexing model from the issue text.