Enable parquet filter pushdown (`filter_pushdown`) by default

[alamb]

In #3380 @thinkharderdev added support for evaluating filters during the parquet scan via the RowIndex mechanism 🎉

This feature is currently enabled via a feature flag, which is disabled by default.

This ticket tracks enabling this feature by default.

Currently known items are:

• Add benchmarks for parquet queries with filter pushdown enabled #3457
• Review of parquet test coverage and add additional coverage as needed: Correctness integration test for parquet filter pushdown #3976
• Incorrect results with parquet filtering pushdown enabled #4005
• Internal error when parquet predicate pushdown is enabled "Error evaluating filter predicate:" #4006
• Another Internal error when parquet predicate pushdown is enabled "Error evaluating filter predicate: #4046
• Enable this feature by default: Enable Parquet Row and Page Filtering by default (WIP) #3828

[alamb]

I plan to review the parquet test coverage over the next day or two

My basic plan is to:

1. Make a draft PR that enables pushdown by default and see if any regression tests fail
2. Do some manual testing using datafusion-cli and some internal datasets

[alamb]

The PR that enables the feature is #3828 and it looks quite promising

Also, I have a proposed config change that I would like to get in, #3822, which would allow users to quickly disable this feature if they found issues

[alamb]

Update here: I am working on some fuzz testing for the predicate pushdown code

[alamb]

I found a bug in pushdown by writing a test #4005

[alamb]

I found another one with my test. I will keep the list on this ticket updated

[alamb]

I think we are getting close