[Bug] The BETWEEN operator reported an internal error.

### 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 t1 BETWEEN (0) AND (100.0)

# query 2 error
SELECT t1 FROM root.db0 WHERE 1 BETWEEN (t1) AND (100.0)
```

### What did you expect to see?

Query 1 returned result set: 0.1 and 0.2

Query 2 returned result set: 0.1 and 0.2

### What did you see instead?

Query 1 returned result set: 0.01 and 0.02

Query 2 reported an internal error: Msg: org.apache.iotdb.jdbc.IoTDBSQLException: 305: [INTERNAL_SERVER_ERROR(305)] Exception occurred: "SELECT t1 FROM root.db0 WHERE 1 BETWEEN (t1) AND (100.0)". executeStatement failed. java.lang.Long cannot be cast to java.lang.Double

### Anything else?

Dear IoTDB team, I think this might be a bug. If this functionality is not supported, should relevant information be returned to inform the user of the error reason, instead of a 305 internal error?

### Are you willing to submit a PR?

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

Comienza reproduciendo las dos consultas BETWEEN del issue contra IoTDB 1.3.3 y, a continuación, sigue la ruta de consulta que gestiona los tipos de operandos y las comparaciones numéricas. Se considera completado cuando la segunda consulta devuelve las filas esperadas sin un error interno y el resultado numérico incorrecto de la primera consulta se ha corregido o se informa mediante un error claro para el usuario.

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