Request corresponding error message for keyword conflicts.

[DanielWang2035]

In 0.13.0, executing select * from root.global.** in cli will raise an error: Msg: 401: Error occurred while parsing SQL to physical plan: line 1:19 mismatched input 'global' expecting {'*', '**', STRING_LITERAL, INTEGER_LITERAL, ID, QUTOED_ID_IN_NODE_NAME} This is because 'global' is a keyword in iotdb. Though the statement select * from root.`global`.** is supported, the error message is not telling users there's been a keyword conflict.

Here are some possible solutions:

1. Add a message code representing keyword conflicts.
2. Show warnings when user try to use keywords in paths.

Also, creating or selecting from root.global.** is not allowed in cli, but is ok in Java native api.

[github-actions[bot]]

Hi, this is your first issue in IoTDB project. Thanks for your report. Welcome to join the community!