Bump HikariCP from 2.6.1 to 3.2.0 in /modules/spock

[dependabot-preview]

Bumps HikariCP from 2.6.1 to 3.2.0.

Changelog

Sourced from HikariCP's changelog.

HikariCP Changes

Changes in 3.2.0

• check connection closed condition before attempting to set network timeout to avoid spurios exceptions
  in the log.

• updated validation failure message to include recommendation to check maxLifetime value.

• fixed 1141 do not throw SQLException when calling isClosed() or close() on a already closed unwrapped
  Connection, as per JDBC specification.

• fixed 1137 support changing user/password at runtime for DriverDataSource-wrapped driver connections.

• fixed 1136 log loaded driver when using jdbcUrl.

• pull 1135 extract sealed pool check into independent method.

• fixed 1126 correct error in JavaDoc for HikariConfig.setInitializationFailTimeout().

• fixed 1114 removed unreachable code.

Changes in 3.1.0

• Add get/setCatalog() to HikariConfigMXBean, allowing the catalog to be changed at runtime.
  The catalog should only be changed while the pool is suspended, and after evicting existing
  connections via HikariPoolMXBean.softEvictConnections().

Changes in 3.0.0

• Removed previously deprecated methods;
  HikariConfig.copyState()
  HikariConfig.getScheduledExecutorService()
  HikariConfig.setScheduledExecutorService()
  HikariConfig.isInitializationFailFast()
  HikariConfig.setInitializationFailFast()
  HikariConfig.isJdbc4ConnectionTest()
  HikariConfig.setJdbc4ConnectionTest()

  HikariDataSource.copyState()
  HikariDataSource.getScheduledExecutorService()
  HikariDataSource.setScheduledExecutorService()
  HikariDataSource.suspendPool()
  HikariDataSource.resumePool()
  HikariDataSource.shutdown()
  HikariDataSource.isInitializationFailFast()
  HikariDataSource.setInitializationFailFast()
  HikariDataSource.isJdbc4ConnectionTest()
  HikariDataSource.setJdbc4ConnectionTest()

... (truncated)

Commits

• ad827db [maven-release-plugin] prepare release HikariCP-3.2.0
• 0f06b56 Update pom.xml
• 3498a14 Update CHANGES
• 88b57c3 Check closed condition before attempting to set network timeout.
• 6a13980 Update validation failure message.
• 603951f Fixes #1126 correct error in JavaDoc for HikariConfig.setInitializationFailTi...
• 5607d8b Fixes #1141 do not throw SQLException when calling isClosed() or close() on a...
• 8921bb0 Fixes #1137 support changing user/password at runtime for DriverDataSource-wr...
• 851e2d4 Fixes #1137 support changing user/password at runtime for DriverDataSource-wr...
• 71e8688 Closes #1114 Remove unneeded code.
• Additional commits viewable 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.

---

Note: This repo was added to Dependabot recently, so you'll receive a maximum of 5 PRs for your first few update runs. Once an update run creates fewer than 5 PRs we'll remove that limit.

You can always request more updates by clicking Bump now in your Dependabot dashboard.

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 cancel merge will cancel a previously requested merge
• @dependabot reopen will reopen this PR if it is closed
• @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 the .dependabot/config.yml file in this repo:

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

Finally, you can contact us by mentioning @dependabot.