feat(error-log-logger): add clickhouse for error-log-logger

[qizhendong1]

What this PR does / why we need it:

Add error-log-logger supports clickhouse.

Pre-submission checklist:

• Did you explain what problem does this PR solve? Or what new features have been added?
• Have you added corresponding test cases?
• Have you modified the corresponding document?
• Is this PR backward compatible? If it is not backward compatible, please discuss on the mailing list first

[tzssangglass]

Now that we have the clickhouse plugin, can we implement it in this plugin?

I am concerned that this will introduce duplicate code.

[spacewander]

What does this sentence mean?

[qizhendong1]

it's means that the plugins insert error logs to the clickhouse table with data column default.

[qizhendong1]

┌─data──────────────────────────────────────────────────────────────────┬
│  2022/02/16 16:45:07 [error] 4279#4279: *7272 [lua] batch-processor.lua:73: Batch ...                                  │ 
└───────────────────────────────────────────────────────────────────────┴

[spacewander]

Is it possible to verify the reported error log in the test?

[qizhendong1]

It is difficult because the error logs are different each other.
clickhouse error log body: INSERT INTO t FORMAT JSONEachRow {"data": " 2022/02/16 16:45:07 [error] 4279#4279: *7272 [lua] batch-processor.lua:73: Batch ... "}

[qizhendong1]

Now that we have the clickhouse plugin, can we implement it in this plugin?

I am concerned that this will introduce duplicate code.

I think it is a good idea. One side we can reduce duplicate code, antoher avoid error-log-logger.lua oversize. It is friendly for new plugin.

@spacewander How about you ？

[spacewander]

No.
@tzssangglass
Handling the error log and access log are two different things. The former needs to be configured at the global level, the latter can be done in a smaller scope.

[tzssangglass]

The former needs to be configured at the global level

I got. Let's keep it that way for now and leave the optimization for later.

[tzssangglass]

is there log body releated to "this is a warning message for test5."?

[qizhendong1]

yes, I will add it.

[qizhendong1]

There is a test case failed. How to fix it ? @spacewander @tzssangglass @leslie-tsang
https://github.com/apache/apisix/runs/5282480987?check_suite_focus=true#step:6:4

Run ./utils/check-category.py
Entry docs/zh/latest/plugins/datadog.md in the sidebar can't be found. Please remove it from docs/zh/latest/config.json.
Error: Process completed with exit code 2[5](https://github.com/apache/apisix/runs/5282480987?check_suite_focus=true#step:6:5)5.

[spacewander]

Thanks for your report. I am fixing it via #6411

[leslie-tsang]

Hello there, Plz don't force push during the review.

Commit history allows reviewers to see what has changed since the last review, which is useful for them.

A forced push could ruin the review experience.

[tzssangglass]

LGTM, @zhendongcmss CI/build was failed, I will rerun it and if it still fails, we need to focus on it.