Enable full predicate pushdown for decimal type in ClickHouse connector

[sylph-eu]

Description

Partially resolves #7100.

This PR reworks decimal type support by ClickHouse connector and makes implementation similar to the one by e.g. MySQL or Postgres connectors. As the result it enables full predicate pushdown.

Changes:

• Columns are ignored (unless it's configured to treat it as varchar) if precision exceeds maximum value (38).
• ClickHouse doesn't support negative scale, however it's coded nonetheless.

It's worth noting that ClickHouse implements Decimal in a slightly nuanced way (link):

1. Excessive digits in a fraction are discarded (not rounded). Excessive digits in integer part will lead to an exception. There's a unit test for that.
2. Overflow check is not implemented for Decimal128 and Decimal256. In case of overflow incorrect result is returned, no exception is thrown. Trino supports precision up to 38 digits which is therefore implemented by Decimal128.

Additional context and related issues

Please review previous PRs related to ClickHouse connector as the number of changes keep accumulating.

Next I'm going to focus predicate pushdown for time types and on aggregate functions.

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:

# Section
* Enable decimal full predicate pushdown for ClickHouse connector. ({issue}`7100`)

[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

[github-actions]

Closing this pull request, as it has been stale for six weeks. Feel free to re-open at any time.