Produce DictionaryBlock when reading parquet dictionary encoded columns

[raunaqmorarka]

Description

Switch to producing DictionaryBlock from FlatColumnReader when a column
is encoded fully using dictionary encoding and the count of rows read
from the column chunk are larger than the size of the dictionary.
We continue to resolve dictionary ids as before when there is a mix of
dictionary and other encodings to keep the implementation simpler.
DictionaryBlock creation is restricted to variable width data types
where dictionary processing is most beneficial.

Benchmark                     (benchmarkFileFormat)    (compression)           (dataSet)   Mode Cnt  Score Before    Score After      Units
BenchmarkHiveFileFormat.read  TRINO_OPTIMIZED_PARQUET           NONE            LINEITEM  thrpt  15  12.900 ± 0.209   21.332 ± 0.895  ops/s
BenchmarkHiveFileFormat.read  TRINO_OPTIMIZED_PARQUET           NONE       VARCHAR_SMALL  thrpt  15  12.210 ± 0.469  114.673 ± 3.483  ops/s
BenchmarkHiveFileFormat.read  TRINO_OPTIMIZED_PARQUET           NONE       VARCHAR_LARGE  thrpt  15  12.056 ± 0.737  116.865 ± 1.482  ops/s
BenchmarkHiveFileFormat.read  TRINO_OPTIMIZED_PARQUET           NONE  VARCHAR_DICTIONARY  thrpt  15   9.555 ± 0.729  164.582 ± 4.742  ops/s

Additional context and related issues

Fixes #2020

Release notes

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

# Hive, Hudi, Delta, Iceberg
* Improve performance of queries with filters or projections on low cardinality string columns stored in parquet files. ({issue}`15269`)

[sopel39]

I understand this is on hold due to regression?

[sopel39]

approved, we probably need to address other dictionary issues first

[martint]

Why does the method name indicate "block"?

[raunaqmorarka]

The important thing inside ColumnChunk is a "block".
The existing class "ColumnChunk" is not appropriately named because we're returning a batch of rows from a parquet column chunk in the form of a block rather than the column chunk.

[martint]

How is this different from ColumnAdapter? There seems to be some overlap.

[raunaqmorarka]

This owns state (buffer containing values for current batch) while ColumnAdapter doesn't.
It also keeps track of count of nulls in the current batch and uses that to produce RLE block of nulls if all values are nulls or a non-block for a nullable column if the current batch had no nulls.
It's not doing anything type specific whereas ColumnAdapter is mainly about things that need to be done differently for various types.

[raunaqmorarka]

Parquet dictionary block sf1k partitioned.pdf

Parquet dictionary block sf1k unpartitioned.pdf

TPC results showed regressions for some queries if we tried to use dictionary blocks for all types (despite restricting dictionary blocks only to cases where the entire column chunk is dictionary encoded and the filtered row count is greater than dictionary size).
When it's restricted to only variable width types, we see small improvements overall. This makes the implementation consistent with ORC reader which also produces dictionary only for strings.