Add server setting aggregate_function_group_array_max_element_size.

[KochetovNicolai]

Changelog category (leave one):

• Improvement

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

Added server setting aggregate_function_group_array_max_element_size. This setting is used to limit array size for groupArray function at serialization. The default value is 16777215.

Note: initially, the value was hardcoded. The check was working on deserialization only. It was possible to insert some data, but never read in again. The server setting is a work-around for such a case.

Repro:

create table tab3 (x AggregateFunction(groupArray, Array(UInt8))) engine = MergeTree order by tuple();
insert into tab3 select groupArrayState([zero]) from zeros(0x1000000);
select length(groupArrayMerge(x)) from tab3;

SELECT length(groupArrayMerge(x))
FROM tab3

Query id: b98ae84b-deaf-4c31-834c-741166411da7


0 rows in set. Elapsed: 0.031 sec. 

Received exception from server (version 23.8.1):
Code: 128. DB::Exception: Received from localhost:9000. DB::Exception: Too large array size (maximum: 16777215): (while reading from part /home/ubuntu/test/clickhouse/store/5e9/5e93da3c-7033-47dd-8011-7ecb427f50fa/all_1_1_0/ in table default.tab3 (5e93da3c-7033-47dd-8011-7ecb427f50fa) located on disk default of type local, from mark 0 with max_rows_to_read = 1): While executing MergeTreeInOrder. (TOO_LARGE_ARRAY_SIZE)

[robot-ch-test-poll1]

This is an automated comment for commit 26c7dd2 with description of existing statuses. It's updated for the latest CI running
The full report is available here
The overall status of the commit is 🟡 pending

Check name	Description	Status
CI running	A meta-check that indicates the running CI. Normally, it's in success or pending state. The failed status indicates some problems with the PR	🟡 pending
Mergeable Check	Checks if all other necessary checks are successful	🟢 success