Apply Partition pruning before reading files during planning

Partition pruning still tries to read Parquet files during the planning stage even though they don't match the partition filter.

For example, if there were an invalid Parquet file in a directory that should not be queried:

0: jdbc:drill:zk=local> select sum(price) from dfs.tmp.purchases where dir0 = 1;
Query failed: IllegalArgumentException: file:/tmp/purchases/4/0_0_0.parquet is not a Parquet file (too small)

The reason is that the partition pruning happens after the Parquet plugin tries to read the footer of each file.

Ideally, partition pruning would happen first before the format plugin gets involved.