File partitioning for ListingTable

[rdettai]

Which issue does this PR close?

Closes#1139.

Rationale for this change

Adding capability to parse file partitioning and prune unnecessary files

What changes are included in this PR?

• add partition_values: Vec<ScalarValue> to PartitionedFile
• implement pruned_partition_list
• add extra column for the partition dimensions to execute() record batch result in file format execution plans
  • avro/csv/json
  • parquet
• add the proper TableProviderFilterPushDown value to supports_filter_pushdown() to avoid re-evaluation of the partition pruning [1]]

What changes are planned in further issues/PRs?

• Make table partitioning accessible in register/read APIS #1185
• Implement statistics estimation for partition columns #1186
• Optimize how table partitions are pruned #1187

Are there any user-facing changes?

Rename the ListingOptions.partitions to ListingOptions.table_partition_cols to make it a bit more explicit.

---

[1] re-evaluating the filters on the the partition column would be expensive:

• it requires the the column to be pushed down, thus materialized in the source execution plan. This is acceptable if we use DictionaryArray<uint8> which is pretty cheap.
• when applying the filtering expression the dictionary needs to be expanded because many kernel ops are not supported on Dictionaries for now (link and Add better and faster support for dictionary types #87). This could be very expensive!!!!