[CBRD-25708] Enable partition pruning when the partition key is a function expression and the WHERE clause uses the original column

[Hamkua]

http://jira.cubrid.org/browse/CBRD-25708

In CUBRID, when an expression is specified as the partition key, partition pruning can only occur if the same expression is compared to a constant value in the query's WHERE clause.
However, if the original column included in the expression is compared with a constant value in the condition, partition pruning does not work.

Therefore, this feature has been added to support partition pruning even when the original column in the expression is compared with a constant value in the WHERE clause.

When comparing the PRED_EXPR of type EVAL_TERM in where_pred and where_key, the types of the original column in the partition key expression and the constant value are checked for compatibility.
If they are compatible, the original column in the expression is replaced with the constant value, allowing the partition key value to be computed accordingly.

[Hamkua]

파티션 키가 아닌 컬럼을 포함한 집합을 조건절에서 비교하는 경우, 파티션 프루닝이 불가능한 문제가 있습니다.

예:

drop table if exists t1;
create table t1(c1 int, c2 int) partition by range(c1) (
    partition p1 values less than (10),
    partition p2 values less than (20),
    partition p3 values less than (30),
    partition p4 values less than (40)
);

insert into t1 values (3, 1), (6, 2), (9, 3), (12, 4), (15, 5), (18, 6), (21, 7), (24, 8), (27, 9), (30, 10);

/* c1에 해당하는 5, 10이 상수 값임에도, 파티션 프루닝 불가능 */
select /*+ recompile */ * from t1 where (c1, c2) in ((5, 1),(10, 2));