`NAME_CONST` accepts different kind of arguments compared with MySQL

## Bug Report

Please answer these questions before submitting your issue. Thanks!

### 1. Minimal reproduce step (Required)

### 2. What did you expect to see? (Required)

```
mysql> SELECT NAME_CONST('bool1', TRUE);
ERROR 1210 (HY000): Incorrect arguments to NAME_CONST
mysql> SELECT NAME_CONST('bool2', FALSE);
ERROR 1210 (HY000): Incorrect arguments to NAME_CONST
mysql> SELECT NAME_CONST('pi', PI());
+----------+
| pi |
+----------+
| 3.141593 |
+----------+
1 row in set (0.02 sec)
```

### 3. What did you see instead (Required)

```
mysql> SELECT NAME_CONST('bool1', TRUE);
+-------+
| bool1 |
+-------+
| 1 |
+-------+
1 row in set (0.00 sec)

mysql> SELECT NAME_CONST('bool2', FALSE);
+-------+
| bool2 |
+-------+
| 0 |
+-------+
1 row in set (0.00 sec)

mysql> SELECT NAME_CONST('pi', PI());
ERROR 1210 (HY000): Incorrect arguments to NAME_CONST
```

### 4. What is your TiDB version? (Required)