[Bug] The BETWEEN operator suppresses normal syntax parsing.

### Search before asking

- [X] I searched in the [issues](https://github.com/apache/iotdb/issues) and found nothing similar.

### Version

version 1.3.3 (Build: ad95a7e)

### Describe the bug and provide the minimal reproduce step

```
DROP DATABASE root.db0
CREATE DATABASE root.db0

CREATE TIMESERIES root.db0.t1 WITH datatype=DOUBLE compressor=GZIP 'MAX_POINT_NUMBER'='8';
INSERT INTO root.db0(timestamp, t1) VALUES (1676586471999, 0.1);
INSERT INTO root.db0(t1) VALUES (0.2);

# query 1 success
SELECT t1 FROM root.db0 WHERE 1 BETWEEN (0) AND (t1 - CAST(t1 as DOUBLE))

# query 2 error
SELECT t1 FROM root.db0 WHERE (t1 - CAST(t1 as DOUBLE))
```

### What did you expect to see?

Query 1 returned result set: INTERNAL_SERVER_ERROR(305) Unsupported expression type: SUBTRACTION

Query 2 returned result set: INTERNAL_SERVER_ERROR(305) Unsupported expression type: SUBTRACTION

### What did you see instead?

Query 1 returned result set: Empty set.

Query 2 returned result set: INTERNAL_SERVER_ERROR(305) Unsupported expression type: SUBTRACTION

### Anything else?

Dear IoTDB team, Both Query 1 and Query 2 should report syntax errors, but Query 1 executes successfully, which could mislead users.

### Are you willing to submit a PR?

- [X] I'm willing to submit a PR!

Empieza ejecutando la reproducción mínima con IoTDB 1.3.3, centrándote en cómo el analizador SQL procesa las dos expresiones WHERE y la forma BETWEEN. Sigue el punto de entrada del análisis de Query 1 y compáralo con Query 2. Se considera terminado cuando Query 1 ya no se ejecuta correctamente ni devuelve un conjunto vacío cuando la expresión no es válida, y ambos casos informan del error de sintaxis previsto.

Escrito por el modelo de indexación a partir del texto del issue.