improve Client prepared statement setMaxRows implementation

When using max row limitation, current implementation for client prepared statement limits the resultset size only, but on protocol level, all rows will still be unnecessary send in exchanges

When server support it, prefix command with "SET STATEMENT SQL_SELECT_LIMIT=xx FOR " avoid those exchanges, like it's done for Statement and Server prepared statement