Unexpected result when using NULL in BETWEEN

[suyZhong]

Describe the bug
Consider the test case below. It is unexpected that the third query returns true, since the second query returns null, which means that the WHERE clause in the third query should be evaluated to null and thus return an empty result.

To Reproduce

DROP TABLE t0 CASCADE;
DROP TABLE t1 CASCADE;

CREATE TABLE t1(c0 BOOLEAN);
INSERT INTO t1 (c0) VALUES (true);

SELECT * FROM t1; -- true
SELECT (((t1.c0 NOT IN (true)))=((t1.c0 BETWEEN true AND NULL))) FROM t1; -- null
SELECT * FROM t1 WHERE (((t1.c0 NOT IN (true)))=((t1.c0 BETWEEN true AND NULL))); 
-- Expected: Empty set
-- Actual: true

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: c9e0977) (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: @618e73c727b6 (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.

[njnes]

fixed in dec2023, range comparison was incorrectly optimized