Proposal: Add unsafe option to disable UTF8 validation on parquet read

[alamb]

Is your feature request related to a problem or challenge? Please describe what you are trying to do.

It is a pretty common usecase for systems (e.g. InfluxDB 3.0) to ingest data and write it as parquet files and then only ready parquet files that we wrote (and this are well formed)

Doing utf8 validation in the parquet reader take a significant amount of time for string data, likely leading to proposals to improve it like

• Speed up Parquet utf8 validation #6667

However if the usecase is to speed up parquet data that is "trusted" maybe validating at all is unecessary.

Describe the solution you'd like
Add an unsafe parquet API to disable UTF8 validation during read for users

Describe alternatives you've considered

Additional context

[alamb]

We obviously wouldn't use this in DataFusion for clickbench (as it would basically be cheating) but we might very well do so internally in InfluxDB 3.0 or other places where re-validating the same UTF8 data we already wrote consumes CPU unecessarly