ParquetOutputFormat should support custom OutputCommitter

ParquetOutputFormat should support custom OutputCommitter.

There is a need to bypass current Hadoop functionality of writing output data under **_temporary** folder. Especially with AWS S3, there can be huge overhead of moving the files from **_temporary** folder to output folder.

**Reporter**: [Mikko Kupsu](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=mikkokupsu)
**Assignee**: [Steve Loughran](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=stevel@apache.org) / @steveloughran
#### Related issues:
- [Improve Parquet IO Performance within cloud datalakes](https://github.com/apache/parquet-java/issues/2912) (is depended upon by)
#### PRs and other links:
- [GitHub Pull Request #1361](https://github.com/apache/parquet-java/pull/1361)

_{**Note**: *This issue was originally created as [PARQUET-781](https://issues.apache.org/jira/browse/PARQUET-781). Please see the [migration documentation](https://issues.apache.org/jira/browse/PARQUET-2502) for further details.*}

Commencez par ParquetOutputFormat et examinez l’intégration de OutputCommitter de Hadoop, puis lisez la pull request #1361 concernant le travail existant. Le travail est terminé lorsque les committers personnalisés peuvent être pris en charge tout en évitant les écritures inutiles dans _temporary et les déplacements de fichiers sur S3.

Rédigé par le modèle d'indexation à partir du texte de l'issue.