feat(functions): add map_insert function

[hanxuanliang]

I hereby agree to the terms of the CLA available at: https://docs.databend.com/dev/policies/cla/

Summary

part of #15295

Tests

• Unit Test
• Logic Test
• Benchmark Test
• No Test - Explain why

Type of change

• Bug Fix (non-breaking change which fixes an issue)
• New Feature (non-breaking change which adds functionality)
• Breaking Change (fix or feature that could cause existing functionality not to work as expected)
• Documentation Update
• Refactoring
• Performance Improvement
• Other (please describe):

---

This change is 

[hanxuanliang]

However, there is such a description in Snowflake:

If updateFlag is set to TRUE, then the existing input key is updated to the input value

But in Databend, do we support dynamically setting config in the query? Alternatively, we can set the config when querying with the bendsql?

[b41sh]

However, there is such a description in Snowflake:

If updateFlag is set to TRUE, then the existing input key is updated to the input value

But in Databend, do we support dynamically setting config in the query? Alternatively, we can set the config when querying with the bendsql?

We can register a new function with four arguments for map_insert, for example st_geometryfromwkb can support two and three args.

[b41sh]

we can build map domain from key domain and value domain.

[hanxuanliang]

But, I have discovered a problem now:

CREATE TABLE map_insert_test(col_str Map(String, String Null) Not Null, col_int Map(String, Int Null) Null);

SELECT map_insert(col_int, 'a', 100)
FROM map_insert_test;

For the NULL map, it is currently stuck and unable to run. However, I tried to modify the domain calculation, but it had no effect. I have no idea here 😣

[b41sh]

But, I have discovered a problem now:

CREATE TABLE map_insert_test(col_str Map(String, String Null) Not Null, col_int Map(String, Int Null) Null);

SELECT map_insert(col_int, 'a', 100)
FROM map_insert_test;

For the NULL map, it is currently stuck and unable to run. However, I tried to modify the domain calculation, but it had no effect. I have no idea here 😣

Both val_domain and insert_value_domain may be nullable, and we need to deal with various cases, such as

match (val_domain, insert_value_domain) {
    (Domain::Nullable(NullableDomain {..}), Domain::Nullable(NullableDomain {..})) => ...,
    (Domain::Nullable(NullableDomain {..}), _) => ...,
    (_, Domain::Nullable(NullableDomain {..})) => ...,
    (_, _) => ...,
}

[b41sh]

use vectorize_with_builder_3_arg here, so that we can support column values in this function

[b41sh]

if has error, we should return at here.

[b41sh]

EmptyMapType also need support 4 arguments with update_flag, use register_4_arg_core register another function.

[b41sh]

insert_key_domain and insert_value_domain need merge with the key and value domain in source_domain.

[b41sh]

this function can be removed, as we already have register_3_arg_core function

[b41sh]

use register_4_arg_core here like the previous one.