ParquetProperties should not use static ValuesWriterFactory

`ParquetProperties` by default is initialized with static `ValuesWriterFactory`, but during `ParquetProperties` construction `ValuesWriterFactory` is initialized with property. It means that if I construct two `ParquetProperties` with different properties (for example allocators), both will reference a static `ValuesWriterFactory` that would be initialized with the latest `ParquetProperties`. The same problem applies to `DefaultValuesWriterFactory`.

**Reporter**: [Vlad Rozov](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vrozov) / @vrozov
#### Related issues:
- [Add support in Parquet to configure the encoding used by ValueWriters](https://github.com/apache/parquet-java/issues/1966) (is caused by)

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

Comience inspeccionando ParquetProperties, ValuesWriterFactory y DefaultValuesWriterFactory para rastrear cómo se inicializan las fábricas durante la construcción. Reproduzca el problema construyendo dos instancias de ParquetProperties con propiedades diferentes, como allocators, y verifique que cada una use su propia configuración en lugar de la última configurada globalmente. La tarea estará terminada cuando las instancias ya no compartan incorrectamente el estado inicializado de la fábrica.

Escrito por el modelo de indexación a partir del texto del issue.