`TO_SECONDS` is not compatible with MySQL for invalid truncated values.

## 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 TO_SECONDS('2024-03-05XYZ');
+-----------------------------+
| TO_SECONDS('2024-03-05XYZ') |
+-----------------------------+
| 63876816000 |
+-----------------------------+
1 row in set, 1 warning (0.02 sec)

mysql> show warnings;
+---------+------+-------------------------------------------------+
| Level | Code | Message |
+---------+------+-------------------------------------------------+
| Warning | 1292 | Truncated incorrect date value: '2024-03-05XYZ' |
+---------+------+-------------------------------------------------+
1 row in set (0.02 sec)
```

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

```
mysql> SELECT TO_SECONDS('2024-03-05XYZ');
+-----------------------------+
| TO_SECONDS('2024-03-05XYZ') |
+-----------------------------+
| NULL |
+-----------------------------+
1 row in set, 1 warning (0.00 sec)
```

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