Make write.parquet.page-size-bytes and write.parquet.dict-size-bytes taking effect

[kamcheungting-db]

The C++ Parquet writer does not apply write.parquet.page-size-bytes or write.parquet.dict-size-bytes. Both properties are already declared in TableProperties, but passing them through WriterProperties::FromMap has no effect on the underlying Parquet writer configuration.

On the current main, the ParquetWriter::Impl::Open has already configured the compression, compression level, and the row-count limit, however it builds Arrow's writer properties without setting the page or dictionary size. This prevents callers from using the standard Iceberg properties to tune these sizes.

For instance, providing the following properties should configure a 64 KiB data-page target and a 256 KiB dictionary-page limit on output parquet writer:

write.parquet.page-size-bytes=65536
write.parquet.dict-size-bytes=262144

Proposed change:

• Expose these two settings through WriterProperties and apply them when constructing Arrow's Parquet writer properties.
• Use the Iceberg defaults already declared in table_properties.h: 1 MiB for data pages and 2 MiB for dictionary pages.
• Reject invalid or non-positive values before creating the output file.
• Add tests for defaults, overrides, invalid values, and propagation into the underlying writer, plus write/read coverage with custom settings.

Background:

• Java resolves and validates both properties in Parquet.WriteBuilder.Context.dataContext.
• Rust applies them in ParquetWriterBuilder::from_table_properties.

Note:
Byte-based row-group sizing (write.parquet.row-group-size-bytes) can be handled in a separate follow-up because it requires examining the buffering and flush policy.

[kamcheungting-db]

I would handle this case