Add ParquetExec::builder(), deprecate ParquetExec::new

[alamb]

Which issue does this PR close?

Part of #10546

Rationale for this change

While working on #10549 it cumbersome to create a ParquetExec -- there are a few fields on ParquetExec::new that need default values that make it slightly confusing to use.

What changes are included in this PR?

1. Add ParquetExecBuilder and ParquetExec::builder() that handle defaults
2. Add an example and a bunch of docs
3. Deprecate ParquetExec::new
4. Update the code to use the new API

You can see this in action here #10618

Are these changes tested?

Yes, covered by existing tests and new doc example tests

Are there any user-facing changes?

Better docs / examples / builder.

ParquetExec::new() is now deprecated

[waynexia]

Great refactor 👍 Those docs are also brilliant!

A tiny suggestion, we can add #[must_use] to those methods on ParquetExecBuilder to prevent a builder is not .build() at the end.

[alamb]

Thanks @waynexia !

A tiny suggestion, we can add #[must_use] to those methods on ParquetExecBuilder to prevent a builder is not .build() at the end.

I added what I think you are referring to in 70a14dc (though I am not quite sure). Let me know if you had a different idea and I will make that change.

[waynexia]

Something like https://github.com/apache/arrow-rs/blob/12c0d007947a2acb01738a737c3be24f779749f8/arrow-flight/src/arrow.flight.protocol.rs#L501-L523

But after some search, I realized that #[must_use] and the builder pattern don't have a tight association (don't remember why I have such an illusion... 🤣