Forbid writing lower and upper bounds for complex types

[scanhex12]

Writing lower and upper bounds are not supported for complex types

Changelog category (leave one):

• Bug Fix (user-visible misbehavior in an official stable release)

Changelog entry (a user-readable short description of the changes that goes into CHANGELOG.md):

Writing lower and upper bounds are not supported for complex types

Documentation entry for user-facing changes

• Documentation is written (mandatory for new features)

[clickhouse-gh]

Workflow [PR], commit [aa77f8f]

Summary: ❌

job_name	test_name	status	info	comment
Stateless tests (amd_debug, distributed plan, s3 storage, parallel)		failure
	03209_parameterized_view_with_non_literal_params	FAIL
Integration tests (asan, old analyzer, 3/6)		failure
	test_throttling/test.py::test_local_read_throttling_reload	FAIL
Integration tests (aarch64, distributed plan, 4/4)		failure
	test_tcp_handler_interserver_listen_host/test_case.py::test_request_to_node_without_interserver_listen_host	FAIL
	test_tcp_handler_interserver_listen_host/test_case.py::test_request_to_node_with_interserver_listen_host	FAIL
Stress test (amd_msan)		failure
	Server died	FAIL
	Hung check failed, possible deadlock found (see hung_check.log)	FAIL
	Killed by signal (in clickhouse-server.log)	FAIL
	Fatal message in clickhouse-server.log (see fatal_messages.txt)	FAIL
	Killed by signal (output files)	FAIL
	Found signal in gdb.log	FAIL

[antonio2368]

this should be bugfix no?

[scanhex12]

let's keep the label as is

[antonio2368]

let's keep the label as is

Why if it fixes a bug?