bugfix: mysql driver doesn't handle well server side query timeout (Q…

…uery execution was interrupted).

in case we set in the mysql query time limit which is low than executed queries like:

SET GLOBAL MAX_EXECUTION_TIME=1; 
the driver doesn't handle well the error:

1. doesn't parse the error well

2. doesn't report it well

3. will cause connection close due to timeout on the rows _recv_packet() - because the state doesn't enable us to setkeepalive on it.


solution:

in read rows loop we should handle the error, report it, and keep the connection state connected.

tests: update nginx to 1.25.3.

tests: update nginx to 1.25.3.

bumped version to 0.26. (#140)

bumped version to 0.26. (#140)

travis-ci: bumped the NGINX core to 1.21.4. (#135)

travis-ci: bumped the NGINX core to 1.21.4. (#135)

bumped version to 0.24.

bumped version to 0.24.

tests: update test for both ngx_lua_module and stream_ngx_lua_module