fix(cubesql): Calculate proper limit and offset for CubeScan in nested limits case #18744

Job	Run time
latest-tag-sha	18s
build	7m 21s
build-cubestore	4m 28s
unit (20.x)	6m 26s
lint	4m 28s
Build & Test :dev for Debian without pushing	17m 11s
unit (22.x)	6m 18s
docker-image-latest-set-tag	5s
integration-cubestore (20.x)	4m 5s
integration-smoke (20.x)	10m 41s
integration (20.x, clickhouse)	3m 50s
integration (20.x, druid)	3m 42s
integration (20.x, elasticsearch)	3m 19s
integration (20.x, mssql)	3m 47s
integration (20.x, mysql)	4m 32s
integration (20.x, postgres)	3m 41s
integration (20.x, prestodb)	3m 49s
integration (20.x, mysql-aurora-serverless)	3m 14s
integration (20.x, crate)	3m 1s
integration (20.x, mongobi)	3m 24s
	1h 37m 40s

Provide feedback