Fix predicate pushdown for Parquet decimal columns

[alexjo2144]

First four commits are from #9326

The overflow detection constructs a BigDecimal which was missing the decimal scale argument. This resulted in the statistics incorrectly detecting an overflow in many cases.

Example:
Decimal(5, 3) has a maximum value of 99.999. Before the fix, any value over 0.099 would result in an overflow. 0.099 would be represented as 99, which is still lower than the max value, but 0.100 is represented as 100, triggering the overflow logic.

[alexjo2144]

Marking this as a WIP until the base PR is merged

[martint]

Can we separate that last commit from the previous ones? It seems like this is an independent issue and we should be able to fix it without waiting for the other commits.

[alexjo2144]

The expectations here didn't match the code. The encoding is done here using unscaledDecimal https://github.com/trinodb/trino/blob/master/lib/trino-parquet/src/main/java/io/trino/parquet/ParquetTypeUtils.java#L264

[alexjo2144]

Updated to include tests for long decimals as well

[findepi]

The overflow detection constructs a BigDecimal which was missing the decimal scale argument. This resulted in the statistics detecting an overflow any time a decimal is present.

this I do not understand

i know the code was not correct, but i don't see yet why it was incorrect in every case.

other than that -- LGTM

[alexjo2144]

every case was a bit of an overstatement. I updated the PR description to be clearer.