Disable LOGICAL_ERRORs about function monotonicity in release build

[al13n321]

Changelog category (leave one):

• Not for changelog (changelog entry is not required)

Details

I recently added these two LOGICAL_ERRORs that exposed some preexisting bugs: #90461. I'm in the middle of making a stress test to hopefully find and fix most of these bugs. Until that is done, here's a PR to go back to ignoring them for now.

[clickhouse-gh]

Workflow [PR], commit [e84e147]

Summary: ❌

job_name	test_name	status	info	comment
Build (amd_compat)		failure
	Cmake configuration	failure	cidb
Stateless tests (amd_asan, distributed plan, parallel, 1/2)		failure
	02843_context_has_expired	FAIL	cidb
Stateless tests (amd_tsan, s3 storage, parallel)		failure
	00938_fix_rwlock_segfault_long	FAIL	cidb, flaky
Integration tests (amd_tsan, 3/6)		failure
	test_ssh/test.py::test_paramiko_password	FAIL	cidb
AST fuzzer (amd_debug)		failure
	Logical error: 'Invalid number of rows in Chunk Nullable(size = 3, UInt8(size = 3), UInt8(size = 3)) Tuple(size = 1) Int32(size = 3) column Tuple() at position 1: expected 3, got 1'.	FAIL	cidb
BuzzHouse (amd_debug)		failure
	Logical error: 'Inconsistent AST formatting: the query:	FAIL	cidb

[Algunenano]

This is my favorite kind of asserts, as it's finding multiple bugs and preventing further issues. I hope we can enable it back again in release builds too