DataFusion ignores "column order" parquet statistics specification

### Describe the bug

As @tustvold points out, there is a [`column_order` API](https://docs.rs/parquet/latest/parquet/file/metadata/struct.FileMetaData.html#method.column_order) defined in parquet that is currently entirely ignored by DataFusion

It is not entirely clear to me what the implications of ignoring this field are or what other parquet writers populate it with, but we should probably not ignore it

### To Reproduce

_No response_

### Expected behavior

_No response_

### Additional context

To emphasise the point I made when this API was originally proposed, you need more than just the ParquetStatistics in order to correctly interpret the data. You need at least the FileMetadata to get the https://docs.rs/parquet/latest/parquet/file/metadata/struct.FileMetaData.html#method.column_order in order to be able to even interpret what the statistics mean for a given column.

No file or test is identified. Start by locating DataFusion’s Parquet statistics handling and reading parquet::file::metadata::FileMetaData::column_order; establish how column-order semantics affect interpretation of statistics, then add focused coverage for the expected behavior.

Written by the indexing model from the issue text.