Add plain JDBC ApplicationErrorDao implementation

[sleberknight]

• Add JdbcApplicationErrorDao, a plain JDBC implementation of ApplicationErrorDao
• Since the logic to map from a ResultSet is identical for the JDBC and JDBI implementations, move that logic from the Jdbi3ApplicationErrorRowMapper into ApplicationErrorJdbc in a new method 'mapFrom(ResultSet)'. Also, fix how the port is set, using rs.getInt instead of intValueOrNull, since the port field in ApplicationError is an int, not Integer
• Add new constructor accepting only a Throwable to ApplicationErrorJdbc.ApplicationErrorJdbcException
• Add a helper method to ApplicationErrorJdbc for the JDBC implementation, nextOrThrow
• Add abstract base test class, AbstractJdbcApplicationErrorDaoTest, and two subclasses for testing against H2 and Postgres. The base test class uses transaction rollback so that tests execute in a transaction but are never committed.
• Make sure to shut down the in-memory H2 database in both H2Jdbi3ApplicationErrorDaoTest and H2JdbcApplicationErrorDaoTest. Otherwise, if the H2 JDBI test runs after the JDBC one, the tests fail because they expect the database to be empty. By shutting the in-memory database down, we ensure the tests are completely isolated.
• Add TestHelpers test utility with one method, shutdownH2Database, to shut down an H2 database

Misc:

• Remove two redundant warning suppression annotations from ErrorContextUtilitiesTest

Closes #248

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

84.2% Coverage
0.0% Duplication