Bump jdbi3-core from 3.12.2 to 3.13.0

[dependabot-preview]

Bumps jdbi3-core from 3.12.2 to 3.13.0.

Changelog

Sourced from jdbi3-core's changelog.

3.13.0

• Kotlin: respect default values in methods when passed null, #1690
• Arguments.bindingNullToPrimitivesPermitted helps you catch erroneous binding of null to a primitive type
• preparable Arguments: re-invoke prepare on each copy, to propagate updated configuration

Commits

• 35b540a [maven-release-plugin] prepare release v3.13.0
• b236118 Simple DI pattern
• 2319504 Re-prepare factories on each copy of Arguments, so that they can get updated ...
• afc6bc9 implement #1675: forbid binding null for primitives
• 8d2d62f release notes #1690
• a52bd61 Use kotlin default for null columns (#1690)
• 2fd27b0 upgrade h2 to 1.4.200
• be87d39 #1652 useful toString for KotlinPropertyArguments
• 9411f9f [maven-release-plugin] prepare for next development iteration
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

[jhejderup]

Updating org.jdbi:jdbi3-core from 3.12.2 to 3.13.0 introduces no impactful changes in the metrics-jdbi3 module of this project. The update should be safe to make.

Uppdatera, a usage-based static analysis tool for dependency updates that I am developing identified the following call paths to this dependency and none of these calls changed functionality in this new update:

• 
  Sample Call Path(s)

  com.codahale.metrics.jdbi3.InstrumentedSqlLogger.log
  
        at: org.jdbi.v3.core.statement.StatementContext.getElapsedTime
  
  

• 
  Sample Call Path(s)

  com.codahale.metrics.jdbi3.strategies.DefaultNameStrategy$1.getStatementName
  
        at: org.jdbi.v3.core.statement.StatementContext.getRawSql
  
  

  com.codahale.metrics.jdbi3.strategies.DefaultNameStrategy$1.getStatementName
  
        at: org.jdbi.v3.core.statement.StatementContext.getRawSql
  
  

• 
  Sample Call Path(s)

  com.codahale.metrics.jdbi3.strategies.DefaultNameStrategy$2.getStatementName
  
        at: org.jdbi.v3.core.statement.StatementContext.getExtensionMethod
  
  

...calls to getType(), getMethod() omitted

To be on the safe side, I did a quick code review of the diff between the current and new versions of the jar source: there are in total 5 changed functions in two classes---org.jdbi.v3.core.argument.Arguments and org.jdbi.v3.core.config.ConfigRegistry--- that seems to not affect the analyzed module.