expression: fix the bug that cannot perform vectorized expression evaluation (#15902)

[sre-bot]

cherry-pick #15902 to release-4.0

---

What problem does this PR solve?

Related to: #issue15718, #PR15144
It should be possible to perform vectorized expression evaluation when the select statement contains constants

What is changed and how it works?

When the select statement contains constants, it can perform vectorized expression evaluation.
It can be verified by the following example：

drop table tt;
create table tt(a decimal(10, 0), b varchar(1));
insert into tt values(0, '2'), (7, null), (7, '3'), (NULL, 'w'), (NULL, '2'), (NULL, '2'), (NULL, NULL), (7, 'f');

Before this PR:

mysql> select a and b as c, a, b, 1 from tt;
+---+------+------+---+
| c | a    | b    | 1 |
+---+------+------+---+
| 0 |    0 | 2    | 1 |
| NULL |    7 | NULL | 1 |
| 1 |    7 | 3    | 1 |
| 0 | NULL | w    | 1 |
| NULL | NULL | 2    | 1 |
| NULL | NULL | 2    | 1 |
| NULL | NULL | NULL | 1 |
| 0 |    7 | f    | 1 |
+---+------+------+---+
8 rows in set, 2 warnings (0.00 sec)

After this PR: (The answer is wrong. It can be fixed by #15891 )

mysql> select a and b as c, a, b, 1 from tt;
+---+------+------+---+
| c | a    | b    | 1 |
+---+------+------+---+
| 0 |    0 | 2    | 1 |
| 0 |    7 | NULL | 1 |
| 1 |    7 | 3    | 1 |
| 0 | NULL | w    | 1 |
| 0 | NULL | 2    | 1 |
| 0 | NULL | 2    | 1 |
| 0 | NULL | NULL | 1 |
| 0 |    7 | f    | 1 |
+---+------+------+---+
8 rows in set, 2 warnings (0.00 sec)

[sre-bot]

/run-all-tests

[SunRunAway]

LGTM

[XuHuaiyu]

LGTM

[sre-bot]

/run-all-tests

[sre-bot]

@sre-bot merge failed.

[AilinKid]

LGTM

[SunRunAway]

/merge

[sre-bot]

Your auto merge job has been accepted, waiting for 15776, 15889, 15926, 15889, 15861, 15955, 15860, 15868, 15907

[zz-jason]

/merge

[sre-bot]

Your auto merge job has been accepted, waiting for 15907

[sre-bot]

/run-all-tests

[sre-bot]

@sre-bot merge failed.

[sre-bot]

/run-all-tests

[sre-bot]

/run-all-tests

[sre-bot]

@sre-bot merge failed.