InternalParquetRecordWriter doesn't use min/max row counts

PARQUET-99 added settings to control the min and max number of rows between size checks when flushing pages, and a setting to control whether to always use a static size (the min). The [InternalParquetRecordWriter has similar checks](https://github.com/apache/parquet-mr/blob/master/parquet-hadoop/src/main/java/org/apache/parquet/hadoop/InternalParquetRecordWriter.java#L143) that don't use those settings. We should determine if it should update it to use those settings or similar.

**Reporter**: [Ryan Blue](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rdblue) / @rdblue
#### Related issues:
- [Min/Max record counts for block size checks are not configurable](https://github.com/apache/parquet-java/issues/2038) (duplicates)
- [Large rows cause unnecessary OOM exceptions](https://github.com/apache/parquet-java/issues/1584) (is related to)
#### PRs and other links:
- [GitHub Pull Request #495](https://github.com/apache/parquet-mr/pull/495)

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

Commencez dans parquet-hadoop/src/main/java/org/apache/parquet/hadoop/InternalParquetRecordWriter.java vers la ligne 143 et comparez ses vérifications de flush des pages avec les paramètres introduits par PARQUET-99. Examinez la pull request #495 et les issues associées avant de déterminer le comportement attendu ; le travail est terminé lorsque le writer gère systématiquement les nombres minimal et maximal configurables de lignes, ou documente pourquoi il ne devrait pas le faire.

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