bug: the order of offset and limit in the parser is fixed

[yezizp2012]

Describe the bug

limit must be placed before offset, It behaves differently with PG. PG does not have this requirement.
In RW:

dev=> explain select * from pg_type order by oid offset 1 limit 1;
ERROR:  Failed to run the query

Caused by:
  sql parser error: expected end of statement, found: limit
dev=> explain select * from pg_type order by oid limit 1 offset 1;
                                                                                                           QUERY PLAN
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
 BatchTopN { order: [pg_type.oid ASC], limit: 1, offset: 1 }
 └─BatchScan { table: pg_type, columns: [oid, typname, typelem, typarray, typinput, typnotnull, typbasetype, typtypmod, typcollation, typlen, typnamespace, typtype, typdelim, typrelid, typdefault, typcategory, typreceive] }
(2 rows)

In PG:

metadata=> explain select * from pg_type order by oid limit 1 offset 1;
                                         QUERY PLAN
--------------------------------------------------------------------------------------------
 Limit  (cost=0.34..0.41 rows=1 width=259)
   ->  Index Scan using pg_type_oid_index on pg_type  (cost=0.28..48.66 rows=699 width=259)
(2 rows)

metadata=>  explain select * from pg_type order by oid offset 1 limit 1;
                                         QUERY PLAN
--------------------------------------------------------------------------------------------
 Limit  (cost=0.34..0.41 rows=1 width=259)
   ->  Index Scan using pg_type_oid_index on pg_type  (cost=0.28..48.66 rows=699 width=259)
(2 rows)

Error message/log

No response

To Reproduce

No response

Expected behavior

No response

How did you deploy RisingWave?

No response

The version of RisingWave

No response

Additional context

No response