Simplify ParquetExec::new()

[alamb]

Note there is an alternate approach that is not an API change that uses a dedicated builder in #10636, but then I realized that
there were many fields (like enable_page_index etc that could already be set with builder apis on ParquetExec so making them redundant with ParquetExec seemed uncessary

Which issue does this PR close?

Part of #10546

Rationale for this change

While working on #10549 it was cumbersome
to create a ParquetExec -- specifically there are a few fields on ParquetExec::new that
must always be provided even though they are Options and most of the rest of the options can be set via builder style
APIs like with_schema_adapter_factory

In addition, some fields like schema_adapter_factory can not be set by constructor but are instead set
by builder function with_schema_adapater_factor.

Thus it is confusing and imposes a cognitive load that the properties setting is inconsistent.

What changes are included in this PR?

1. Remove all arguments except FileScanConfig from ParquetExec::new
2. Add builder style APIs
3. Improve documentation
4. Add examples

Are these changes tested?

Yes by existing CI

Are there any user-facing changes?

This is a user API change for anyone who creates ParquetExec's directly (as we do in InfluxDB IOx for example)

There is also better documentation

[alamb]

The more I think about this the more I like #10636 and deprecate the ParquetExec::new function...