null_count is omitted for large columns in parquet files

### Describe the bug, including details regarding any error messages, version, and platform.

Currently in [ParquetMetadataConverter.java](https://github.com/apache/parquet-java/blob/7be05b4702df78ae0c0c6b44adc6b7b7af2d931f/parquet-hadoop/src/main/java/org/apache/parquet/format/converter/ParquetMetadataConverter.java), there is a guard that prevents the writing of statistics such as min/max AND null_count when the stats are larger than the max allowed size under truncation. The rationale for this makes sense for omitting min/max, however null_count can be written on the file despite the size of its content. See the code below:

https://github.com/apache/parquet-java/blob/7be05b4702df78ae0c0c6b44adc6b7b7af2d931f/parquet-hadoop/src/main/java/org/apache/parquet/format/converter/ParquetMetadataConverter.java#L800-L807

The missing `null_count` metadata sometimes causes downstream consumers of the parquet files to error. For example in Snowflake we are seeing the following kind of error:

```
non-nullable column without default has null values according to file statistics
```

### Component(s)

Core

parquet-hadoop/src/main/java/org/apache/parquet/format/converter/ParquetMetadataConverter.java の 800-807 行付近にあるガードから開始してください。現在、サイズ制限によって統計情報がどのように抑制されているかを確認し、そのうえで min/max が省略される場合でも null_count が保持されるようにしてください。大きな列を持つ Parquet ファイルに null_count のメタデータが含まれ、報告されている下流エラーが回避されれば完了です。

索引モデルが issue の本文から書いたものです。