[Enhancement] Use dynamic batch size for simdjson to parse multiple json document

[srlch]

Why I'm doing:

In current implementation, JsonDocumentStreamParser use simdjson::ondemand::parser::iterate_many to parse multiple JSON document. This API need caller pass the max size of JSON document called, says max_json_lenght_in_file in a given file to allocate the a memory chunk to finish the parsing process. But the problem is that, the caller pass the file size instead of max_json_lenght_in_file and allocate huge memory chunk (which may not be used) almost 5~6 time of the file size. This is a huge memory amplification

What I'm doing:

Introduce json_parse_many_batch_size to control the batch_size passed into simdjson::ondemand::parser::iterate_many. If json_parse_many_batch_size > 0, use json_parse_many_batch_size as batch size, otherwise use simdjson::dom::DEFAULT_BATCH_SIZE. For JsonDocumentStreamParser::get_current, parse the doc using a relative small buffer. If an exception is thrown because the buffer is too small, increase the buffer size and retry.

Fixes #issue https://github.com/StarRocks/StarRocksTest/issues/8636

What type of PR is this:

• [ ] BugFix
• [ ] Feature
• [x] Enhancement
• [ ] Refactor
• [ ] UT
• [ ] Doc
• [ ] Tool

Does this PR entail a change in behavior?

• [x] Yes, this PR will result in a change in behavior.
• [ ] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

• [ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
• [x] Parameter changes: default values, similar parameters but with different default values
• [ ] Policy changes: use new policy to replace old one, functionality automatically enabled
• [ ] Feature removed
• [ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

• [x] I have added test cases for my bug fix or my new feature
• [ ] This pr needs user documentation (for new or modified features or behaviors)
  • [ ] I have added documentation for my new feature or new function
• [ ] This is a backport pr

Bugfix cherry-pick branch check:

• [x] I have checked the version labels which the pr will be auto-backported to the target branch
  • [x] 3.4
  • [x] 3.3
  • [ ] 3.2
  • [ ] 3.1
  • [ ] 3.0

[github-actions[bot]]

[Java-Extensions Incremental Coverage Report]

:white_check_mark: pass : 0 / 0 (0%)

[github-actions[bot]]

[FE Incremental Coverage Report]

:white_check_mark: pass : 0 / 0 (0%)

[github-actions[bot]]

[BE Incremental Coverage Report]

:white_check_mark: pass : 28 / 33 (84.85%)

file detail

	path	covered_line	new_line	coverage	not_covered_line_detail
:large_blue_circle:	src/exec/json_parser.h	0	1	00.00%	[77]
:large_blue_circle:	src/exec/json_parser.cpp	28	32	87.50%	[59, 67, 86, 91]