space partition incorrectly excluded for DML based on cross-type comparison

-- DELETE on a hash dimension misses the row when the equality literal
-- has a different type than the partition column (date column, timestamp
-- literal). With timescaledb.enable_optimizations = off the same DELETE
-- removes the row.

CREATE TABLE ferry_sailings (
    departs_at timestamptz NOT NULL,
    route_added_on date NOT NULL
);

SELECT create_hypertable('ferry_sailings', 'departs_at');
SELECT add_dimension('ferry_sailings', 'route_added_on', number_partitions => 2);

INSERT INTO ferry_sailings VALUES ('2024-01-15 08:00:00+00', '2024-01-15');

-- baseline: optimizations off, the row is found
BEGIN;
SET LOCAL timescaledb.enable_optimizations = off;
DELETE FROM ferry_sailings WHERE route_added_on = '2024-01-15'::timestamp; -- DELETE 1
ROLLBACK;

-- default settings: the same statement misses the row
BEGIN;
DELETE FROM ferry_sailings WHERE route_added_on = '2024-01-15'::timestamp; -- DELETE 0, expected DELETE 1
ROLLBACK;