Add bloom filter write support to ParquetWriter

[jkylling]

Description

The bloom filters are added after all the row groups, right before the footer, similar to the first option described here.

We do not support writing bloom filters for types for which we do not have read support.

Additional context and related issues

Fixes #16536

Release notes

( ) This is not user-visible or is docs only, and no release notes are required.
( ) Release notes are required. Please propose a release note for me.
(x) Release notes are required, with the following suggested text:

# Hive
* Add support for writing bloom filters in parquet files to speed up equality and IN predicates on high cardinality columns. ({issue}`20662`)

[raunaqmorarka]

A few things to work on from first look:

• Check where in the parquet file Hive and Spark store the bloom filter (they use parquet-mr directly). We will want to make sure that we're not differing from that.
• We need product tests that files with bloom filter written by trino work on Apache Hive and Spark
• We don't want this getting enabled by default. Users should opt into it on a per-table basis similar to the way bloom filter columns can be specified in ORC in Trino
• BaseTestParquetWithBloomFilters should be updated to use Trino to write bloom filters

[jkylling]

There remains some work to decide on how to configure the bloom filters in Hive (and also Iceberg and Delta). We could do the following:
For the Hive table properties:

parquet.bloom.filter.enabled#<column-name>=true
parquet.bloom.filter.fpp#<column-name>=0.1 # double between 0 and 1
parquet.bloom.filter.expected.ndv#<column-name>=1 # integer between 1 and Long.MAX_VALUE

These are the same properties used by parquet-mr: https://github.com/apache/parquet-mr/blob/20d43639b5a380335953742ad6c9b3dd98e09f29/parquet-hadoop/src/main/java/org/apache/parquet/hadoop/ParquetOutputFormat.java#L152-L155

If any of the Hive table properties have invalid values we treat them as unspecified. parquet.bloom.filter.enabled#<column-name>=true must always be specified for the others table properties to take effect.

For the Iceberg table properties we will likely want to do writer.parquet.bloom-filter-enabled.column.<column-name>, and similar for the other properties, https://iceberg.apache.org/docs/latest/configuration/#write-properties

For the Trino table properties we define:

parquet_bloom_filter_enabled, map(varchar, boolean) = MAP(ARRAY['<column-name>'], ARRAY[<enabled>]]
parquet_bloom_filter_fpp, map(varchar, double) = MAP(ARRAY['<column-name>'], ARRAY[<fpp>]]
parquet_bloom_filter_ndv, map(varchar, bigint) = MAP[ARRAY['<column-name>'], ARRAY[<ndv>]]
parquet_bloom_filters_enabled, boolean. It enables bloom filters for all columns which can support it. If parquet_bloom_filter_columns is also specified, the entries of parquet_bloom_filter_enabled takes precedence.

[github-actions]

This pull request has gone a while without any activity. Tagging the Trino developer relations team: @bitsondatadev @colebow @mosabua

[github-actions]

This pull request has gone a while without any activity. Tagging the Trino developer relations team: @bitsondatadev @colebow @mosabua

[raunaqmorarka]

I've pushed some minor fixups, please apply them into the appropriate commits

[raunaqmorarka]

minor comments, lgtm