Incorrect offset handling on some queries against database with supported LIMIT/OFFSET clauses

Select queries with offset set and suppressed DISTINCT clause running against database like PostgreSQL (with OFFSET/LIMIT clauses supported) are handled incorrectly. Now, DISTINCT suppressing in SelectTranslator also suppress LIMIT/OFFSET SQL query clauses, but in-memory offset returned by SelectAction.getInMemoryOffset() remain unchanged, effectively zeroing offset for these queries against databases like PostgreSQL.