Don't use literal true and false in queries

[sleberknight]

We're using the literal true and false in queries which works for certain databases but not others (hi MySQL).

It might be a good idea to change all the literal booleans to bind parameters, both in JDBI and JDBC implementations.

reference: #316 (comment)

[sleberknight]

Actually, the literals true and false in MySQL are constants that evaluate to 1 and 0, respectively:

mysql> SELECT TRUE, true, FALSE, false;
        -> 1, 1, 0, 0

So our queries which use true and false will work in MySQL. I verified this by creating a test of the JDBI3-based DAO using MySQL. I might actually commit this, since we'll then have tests for H2, Postgres, and MySQL.

reference: https://dev.mysql.com/doc/refman/8.3/en/boolean-literals.html

[sleberknight]

Added MySQL tests in #352

[sleberknight]

Not that we really care about Oracle, but apparently version 23c finally introduced a boolean type.

[sleberknight]

I am closing this as "resolved". We can revisit if it ever becomes an issue, which I highly doubt it will.