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.*}

Start by inspecting ParquetProperties, ValuesWriterFactory, and DefaultValuesWriterFactory to trace how factories are initialized during construction. Reproduce the issue by constructing two ParquetProperties instances with different properties, such as allocators, and verify that each uses its own configuration rather than the latest one globally. Done means the instances no longer share incorrectly initialized factory state.

Written by the indexing model from the issue text.