[Bug] 特定场景 SELECT last * from 语句报错

### Search before asking

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

### Version

2.0.5

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

SELECT last * from root.xx.yy where Time < 1756080000000 and Time > 1755910000000
时能正常查到数据
SELECT last * from root.xx.yy where Time < 1756080000000 and Time > 1755010000000
时间范围变化后，报错：
SQL 错误 [301]: 301: null

类似的
select last `y1`.*,y2.*
from root.xx where Time >= 1756080000000
能查到数据
select last `y1`.*,y2.*
from root.xx
不带条件报错：
SQL 错误 [305] [[INTERNAL_SERVER_ERROR(305)] Exception occurred: "select last `y1`.*,y2.*
from root.xx ". executeStatement failed. Index 4 out of bounds for length 4]: 305: [INTERNAL_SERVER_ERROR(305)] Exception occurred: "select last `y1`.*,y2.*
from root.xx ". executeStatement failed. Index 4 out of bounds for length 4

### What did you expect to see?

无论条件如何，语法没错，不应该报错。另外2.0.2版本没发现这个问题

### What did you see instead?

SQL 错误 [301]
SQL 错误 [305]

### Anything else?

_No response_

### Are you willing to submit a PR?

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

まず IoTDB 2.0.5 で 2 つの SELECT last クエリを再現し、その後、バージョン 2.0.2 と動作を比較します。報告された index-out-of-bounds 失敗を含め、エラー 301 と 305 を発生させるクエリパスを追跡します。指定された時間範囲全体で、条件なしに両方のクエリ形式が正常に実行できれば完了です。

索引モデルが issue の本文から書いたものです。