Add an option for `clickhouse-client` with a list of tests for extensive fuzzing.
Processing of these tests will be interleaved between every other tests, so we will get much better fuzzing coverage.
if (hint.clientError() != e.code())
                {
                    if (hint.clientError())
                        e.addMessage("\nExpected client error: " + std::to_string(hint.clientError()));
                    throw;
                }
                /// It's expected syntax error, skip the line
                this_query_begin = end_of_line;
                continue;
            }
            if (!parsed_query)
            {
                if (ignore_error)
                {
                    Token(this_query_begin, all_queries_end);
                    IParser::Pos token_iterator(tokens, context.getSettingsRef().max_parser_depth);
                    while (token_iterator->type != TokenType::Semicolon && token_iterator.isValid())
                        ++token_iterator;
                    this_query_begin = token_iterator->end;
                    continue;
                }
                return true;
            }
            // INSERT queries may have the inserted data in the query text
            // that follow the query itself, e.g. "insert into t format CSV 1;2".
            // They need special handling. First of all, here we find where the
            // inserted data ends. In multy-query mode, it is delimited by a
            // newline.
            // The VALUES format  more handling -- we also allow the
            // data to be delimited by semicolon. This case is handled later by