[Bug] 'order by name desc' can't work

### Search before asking

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

### Version

1.0.0

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

exec:
'select _state_id_, name from root.G9990002.terminal where _state_id_<='Sck-20-13' order by name desc'

produced a error:
700: Error occurred while parsing SQL to physical plan: line 1:91 no viable alternative at input

However,
select _state_id_, name from root.G9990002.terminal where _state_id_<='Sck-20-13' order by time desc

executed correctly.

### What did you expect to see?

the following sql execute failed:

select _state_id_, name from root.G9990002.terminal where _state_id_<='Sck-20-13' order by name desc

### What did you see instead?

select _state_id_, name from root.G9990002.terminal where _state_id_<='Sck-20-13' order by name desc

can be executed correctly.

### Anything else?

_No response_

### Are you willing to submit a PR?

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

Start by reproducing the reported query and the working `order by time desc` variant against IoTDB 1.0.0, then trace the SQL parsing path for `order by name desc`. Done means the name-sorted query parses and executes consistently while the existing time-sorted query still works.

Written by the indexing model from the issue text.