Add rule for unwrapping TIMESTAMP to DATE cast when comparing with DATE literal

[losipiuk]

Description

Add a rule for unwrapping TIMESTAMP to DATE cast when comparing with DATE literal

Is this change a fix, improvement, new feature, refactoring, or other?

improvement

Is this a change to the core query engine, a connector, client library, or the SPI interfaces? (be specific)

core query engine (optimizer)

How would you describe this change to a non-technical end user or system administrator?

New rule rewrites CAST(ts_column as DATE) OP date_literal to range expression on ts_column. Dropping cast
allows for further optimizations, such as pushdown into connectors.

Documentation

(x) No documentation is needed.
( ) Sufficient documentation is included in this PR.
( ) Documentation PR is available with #prnumber.
( ) Documentation issue #issuenumber is filed, and can be handled later.

Release notes

( ) No release notes entries required.
(x) Release notes entries required with the following suggested text:

# General
* Improve performance of specific queries which compare table columns of type `timestamp` with `date` literals. ({issue}`11170`)

[findepi]

cc @kasiafi

[findepi]

General

Improve performance of specific queries which compare table columns of type timestamp with date literals. ({issue}11170)

this matters especially when timestamp value is a column, and connector supports predicate pushdown.
cc @hashhar @wendigo