Incorrectly range vertices/edges with barrier

### Bug Type (问题类型)

gremlin (结果不合预期)

### Before submit

- [X] 我已经确认现有的 [Issues](https://github.com/apache/hugegraph/issues) 与 [FAQ](https://hugegraph.apache.org/docs/guides/faq/) 中没有相同 / 重复问题 (I have confirmed and searched that there are no similar problems in the historical issue and documents)

### Environment (环境信息)

- Server Version: 1.0.0 (Apache Release Version)
- Backend: RocksDB x nodes, HDD or SSD
- OS: xx CPUs, xx G RAM, Ubuntu 2x.x / CentOS 7.x
- Data Size: xx vertices, xx edges

### Expected & Actual behavior (期望与实际表现)

```
g.V().range(2,3).range(0,1) ==> v[1]
g.V().range(2,3).barrier().range(0,1) ==>{Invalid range: [2, 1)}
```
I create three vertices (e.g., `v1`, `v2`, and `v3`) and range them with `range(2,3)` and `range(0,1)`. We expect one vertex (e.g., `v1`) can be returned.

However, when we execute the second query where a `barrier()` is added between these two range operations, an exception is thrown instead of returning the vertex `v1`.

I can get the correct result in TinkerGraph with the same query.

You can reproduce this issue by adding three vertices using `addV()`.
```
// for example
v1 = g.addV()
v2 = g.addV()
v3 = g.addV()
```

### Vertex/Edge example (问题点 / 边数据举例)

_No response_

### Schema [VertexLabel, EdgeLabel, IndexLabel] (元数据结构)

_No response_