planner: reimplement DEFAULT function to make the behavior consistent with MySQL when looking up the corresponding column (#19709)

[ti-srebot]

cherry-pick #19709 to release-4.0

---

What problem does this PR solve?

Issue Number: close #17807

Problem Summary:

The previous Default function parsed to generate ast.ColumnName, and then further parsed the corresponding column. But in fact, the Default function does not need to obtain the value of the corresponding column from the storage, so it should not be further parsed by ast.ColumnName.

The previous implementation produced many incompatibility issues with MySQL, such as:

• P1-[4.0 bug hunting]-[SQL Plan Management]-Using the DEFAULT() function results in an ambiguous column error #17807
• select b from t order by default(a) will return Unknown column a, even if t has column a.

Have to merge pingcap/parser#1027 first.

What is changed and how it works?

Proposal: xxx

What's Changed:

• Modify the parser so that DEFAULT function is not generated ast.ColumnName.
• Add new field allNames for PlanBuilder and expressionRewriter to record the set of columns that can be used to find in evalDefaultExpr.
• Find the corresponding column in evalDefaultExpr. And frist, it will look for allNames. If it is not found, it will search in expressionRewrite.names.

Check List

Tests

• Unit test

Side effects

Release note

• reimplement DEFAULT function to make the behavior consistent with MySQL when looking up the corresponding column

[ti-srebot]

/run-all-tests

[ti-srebot]

@rebelice you're already a collaborator in bot's repo.

[rebelice]

PTAL @qw4990 @lzmhhh123

[ichn-hu]

LGTM

[qw4990]

LGTM