[Feature request] add limit offset support for influxdb protocol

### Search before asking

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

### Motivation

从influxdb 迁移过来使用influxdb协议适配，假如没有 limit offset支持，简单的分页需求都无法通过这个协议适配器实现，
另外，如果使用java原生client 无法对tag（influxdb概念）进行非等于的查询
例如 influxdb结构
measurementA
tag1
tag2
field1
通过influxdb协议适配器转换后变成了 root.measurementA.tag1.tag2(Device) field1(value)
如果要查询 tag1 in ('1','2') 或 tag1!= '1' 的记录 ，无法使用原生client在一个查询语句中完成,而influxdb协议适配器又不支持limit offset。这就导致按tag为条件查询并分页即无法通过协议适配器完成也无法通过原生client完成

### Solution

_No response_

### Alternatives

_No response_

### Are you willing to submit a PR?

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

Start by locating the InfluxDB protocol adapter and the query-translation entry point, then inspect how tag predicates and pagination are currently handled. Done means the adapter supports LIMIT/OFFSET and allows paginated queries with the described tag conditions in a single query.

Written by the indexing model from the issue text.