[Feature] Stream load support JSON to STRUCT/MAP/ARRAY (backport #45406)

[mergify]

Why I'm doing:

Now, the SR does't support loading JSON to complex type column.

What I'm doing:

This PR adds the support of JSON format loading to STRUCT/MAP/ARRAY type column.

Here are some examples.

create table tbl_complex (col_int int, col_struct struct<key1 int>, col_array array<int>, col_map map<string,int>, col_struct_array struct<key3 array<int>>,
col_struct_map struct<key4 map<string,int>>);


curl --location-trusted -u root:  'http://127.0.0.1:18040/api/db0/tbl_complex/_stream_load' \-X PUT  \-H 'format: json' -d '{"col_int":1,"col_struct":{"key1":1}, "col_map":{"key2":2}, "col_array":[1,2,3], "col_struct_array":{"key3":[2,3,4,5]}, "col_struct_map":{"key4": {"key5":4}}}'

This feature also works for routine load.

Fixes #43101

What type of PR is this:

• BugFix
• Feature
• Enhancement
• Refactor
• UT
• Doc
• Tool

Does this PR entail a change in behavior?

• 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
• 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:

• 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:

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

---

This is an automatic backport of pull request #45406 done by [Mergify](https://mergify.com). ## Why I'm doing: Now, the SR does't support loading JSON to complex type column. ## What I'm doing: This PR adds the support of JSON format loading to STRUCT/MAP/ARRAY type column.

Here are some examples.

create table tbl_complex (col_int int, col_struct struct<key1 int>, col_array array<int>, col_map map<string,int>, col_struct_array struct<key3 array<int>>,
col_struct_map struct<key4 map<string,int>>);


curl --location-trusted -u root:  'http://127.0.0.1:18040/api/db0/tbl_complex/_stream_load' \-X PUT  \-H 'format: json' -d '{"col_int":1,"col_struct":{"key1":1}, "col_map":{"key2":2}, "col_array":[1,2,3], "col_struct_array":{"key3":[2,3,4,5]}, "col_struct_map":{"key4": {"key5":4}}}'

This feature also works for routine load.

Fixes #43101

What type of PR is this:

• BugFix
• Feature
• Enhancement
• Refactor
• UT
• Doc
• Tool

Does this PR entail a change in behavior?

• 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
• 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:

• 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