feat/header: support set chunk header

[caicancai]

close: #817

[caicancai]

LGTM. However, I don't think this is the best place to put this piece of code. Maybe we should move the match logic into the binder.

Besides, for select queries, resolving the header of their results is another challenging work. You can play with DuckDB to learn how it deals with this. Here are some examples:

D create table t(a int);
D select a from t;
┌────────┐
│   a    │
│ int32  │
├────────┤
│ 0 rows │
└────────┘
D select a + a from t;
┌─────────┐
│ (a + a) │
│  int32  │
├─────────┤
│ 0 rows  │
└─────────┘
D select 1+2;
┌─────────┐
│ (1 + 2) │
│  int32  │
├─────────┤
│       3 │
└─────────┘

You can see the header is determined by the expressions. Therefore, I think it is the binder that should be responsible for resolving headers.

Thank you for taking the time to reply to the review over the weekend, and I'll try to revise it later

[caicancai]

I might also want to try the select header, and then mention another PR

[caicancai]

tested

[caicancai]

In the future, I may continue to expand binder_header, in order to select

[caicancai]

LGTM for now. Looking forward for the following improvement!

It's a great honor to complete this task

[caicancai]

@wangrunji0408 Recently, I have been busy with work. I may need to finish this part of work late. I am sorry for that

[wangrunji0408]

@wangrunji0408 Recently, I have been busy with work. I may need to finish this part of work late. I am sorry for that

No hurry. Take your time.