Unexpected result when using AND/OR chain

[suyZhong]

Describe the bug
Consider the test case below. It is unexpected that the third query returns empty table, since the second query returns true, which means that the WHERE clause of AND OR chain in the third query should be evaluated to true and thus return the row in the table.

To Reproduce

DROP TABLE t0 CASCADE;

CREATE TABLE t0(c0 BOOLEAN,  c1 VARCHAR);
INSERT INTO t0 (c0, c1) VALUES (true, true);
CREATE INDEX i0 ON t0(c1 , c0 );

SELECT * FROM t0; -- true, true
SELECT (t0.c1=(t0.c0 OR true))AND(t0.c0) FROM t0; -- true
SELECT * FROM t0 WHERE ((t0.c1=(t0.c0 OR true))AND(t0.c0));
-- expected: true, true
-- actual: empty table

Expected behavior
As mentioned above

Screenshots
N/A

Software versions
Build from source:

> docker exec monetdb-test mserver5 --version --dbname=monetdb
MonetDB 5 server 11.50.0 (hg id: 25da4f1) (64-bit, 128-bit integers)
This is an unreleased version
Copyright (c) 1993 - July 2008 CWI
Copyright (c) August 2008 - 2023 MonetDB B.V., all rights reserved
Visit https://www.monetdb.org/ for further information
Found 503.5GiB available memory, 128 available cpu cores
Libraries:
Compiled by: @08cc21708292 (x86_64-pc-linux-gnu)
Compilation: /usr/bin/cc 
Linking    : /usr/bin/ld

Issue labeling
Bug

Additional context
Add any other context about the problem here.