Remove rewriteBatchedStatements property

[A248]

Fixes #955

[A248]

Interesting to see a test relating to IP range bans failed because of this. It may be a bug in MariaDB-Connector; we'll have to find out.

Recall that the removal of the rewriteBatchedStatements property will have two results: firstly, it will disable the feature of rewriting batched statements in and of itself. Secondly it will enable useServerPrepStmts.

• I don't think range bans even make use of batched statements. I'm not well-versed in ORMLite, but it would seem to me that, since IpRangeBanStorage inserts 1 range ban at a time, there would be no batched statements. I can view the bm_ip_range_bans table in PhpMyAdmin and the schema seems to confirm that inserting a record would not require a batch insert.
• Since we can eliminate batched statements (right?) as being the cause, we are left with useServerPrepStmts. So, I suppose the next course of action is to determine whether useServerPrepStmts is the cause.

[A248]

I see you re-ran the tests. Since they passed, I hope the previous failure is not indicative of a real issue in MariaDB-Connector, BanManager, or even MariaDB. If it is, then it may be a difficult bug to solve.

Granted, the version of MariaDB used by MariaDB4j is somewhat outdated. I myself used to rely on MariaDB4j in LibertyBans, before recently switching to use docker-maven-plugin to create a temporary database. I'm slightly off-topic here, I realize, but perhaps you'd like to consider doing the same -- I'd permit you to re-use the configuration from the LibertyBans build for the BanManager build. You'd need to adjust it to your needs, however, seeing as BanManager will be using Gradle and seeing that you have a different approach to creating a test matrix (running independent Github workflows for each database, rather than testing all databases in the same build).