Use separate ValuesWriterFactory instances for non-default page options when creating ParquetWriter

[hantangwangd]

Fix #22130

Description

The sharing of a single ValuesWriterFactory among multiple ParquetProperties instances with different write options is not thread-safe and may lead to inconsistency issues.

This PR set a new separate ValuesWriterFactory instance into ParquetProperties on its creation when using a non-default writer options, so that it could work well in multi-thread environment.

Test Plan

• Make sure this change do not affect existing test cases

Contributor checklist

• Please make sure your submission complies with our development, formatting, commit message, and attribution guidelines.
• PR description addresses the issue accurately and concisely. If the change is non-trivial, a GitHub Issue is referenced.
• Documented new properties (with its default value), SQL syntax, functions, or other functionality.
• If release notes are required, they follow the release notes guidelines.
• Adequate tests were added if applicable.
• CI passed.

Release Notes

== NO RELEASE NOTE ==

[hantangwangd]

@elharo Thanks for your suggestion, they have been fixed! Please take a look when available.

[tdcmeehan]

Thanks for fixing this! Just one nit.

[tdcmeehan]

Looks good, but commit message is too long. Perhaps reword as follows:

Fix ValuesWriterFactory in ParquetReader thread safety

The sharing of a single `ValuesWriterFactory` among multiple
`ParquetProperties` instances with different write options is not
thread-safe and may lead to inconsistency issues.

[hantangwangd]

Looks good, but commit message is too long. Perhaps reword as follows:

......

Thanks for the suggestion, fixed!