[Bug] There is a logical error in the precedence of arithmetic operators.

### 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=INT32;
INSERT INTO root.db0(timestamp, t1) VALUES (1641024000000, 0);

# query 1
SELECT (t1 * -1000) FROM root.db0

# query 2
SELECT (t1 * (-1000)) FROM root.db0
```

### What did you expect to see?

Query 1 returned result set: **-0**

Query 2 returned result set: **-0**

### What did you see instead?

Query 1 returned result set: **-1000**

Query 2 returned result set: **-0**

### Anything else?

Dear IoTDB team, In the above scenario, we combine the `unary negation operator` with column t1 and perform a multiplication operation to examine the result returned by IotDB. In Query 1, we did not enclose `-t1` in parentheses to treat it as a whole, and the returned result was **-1000**, which does not match our expectations. In principle, the unary negation operator should have a higher precedence than the multiplication operator, and the presence or absence of parentheses should not affect the final result.

### Are you willing to submit a PR?

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

Le payload ne mentionne aucun fichier d’implémentation ni aucun test. Commencez par exécuter la reproduction minimale de l’issue avec IoTDB et comparer query 1 à query 2 ; c’est terminé lorsque les deux expressions produisent le résultat équivalent attendu, la négation unaire ayant la priorité sur la multiplication.

Rédigé par le modèle d'indexation à partir du texte de l'issue.