…che#51471)

Add new jdbc catalog property: `function_rules`.
This property will enable user to customize which function can be pushed
down to jdbc datasource,
and which function should be rewrote to function in jdbc datasource:

eg:
```
create catalog jdbc properties (
    ...
    'function_rules' = '{"pushdown" : {"supported": ["to_date"], "unsupported" : ["abs"]}, "rewrite" : {"to_date" : "date2"}}'
)
```
The value is a json format config:
- `pushdown`: the value of `pushdown` is a map, the `supported` array
indicate the function that can be pushed down to datasource. the
`unsupported` array indicate the function that can not.
- `rewrite`: the value of `rewrite` is map, if the function can be
pushed down to datasource, it will be renamed to the value in rewrite
map.

eg:
```
select * from jdbc_table where abs(k1) > 0 and to_date("k2") = "2022-10-10"
```
will generate sql:
```
select * from jdbc_table where date2("k2") = "2022-10-10"
```

You can see the `abs()` is not pushed down, and `to_date()` is rewrote
to `date2()`.

-------
This change is compatible with previous version.
Previously, there are some hard coded function rules, and also a FE
config `jdbc_mysql_unsupported_pushdown_functions`.

Doris will merge the user specified `function_rules` and the above
rules.