Set Hikari connection timeout to 60 seconds

[arnejduranovic]

This PR fixes a bug where Hikari config was not respecting the value of 60000ms for the connection timeout. It is also the hope that this change helps address the issue described in the following incident report: https://cdc.sharepoint.com/:w:/r/teams/ReportStream/_layouts/15/Doc.aspx?sourcedoc=%7B2E1169CA-B921-4CAA-B0E6-2BEF7443A1D7%7D&file=2025_02_18%20-%20Database%20Connectivity%20Issues.docx&action=default&mobileredirect=true

Test Steps:

1. Start up the app and verify the hikari config has the connection timeout property set to 60000 on this branch and 30000 on main:
   

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

OpenSSF Scorecard

Package	Version	Score	Details

Scanned Manifest Files

[github-actions]

Test Results

1 280 tests  ±0   1 276 ✅ ±0   7m 48s ⏱️ +19s
  168 suites ±0       4 💤 ±0 
  168 files   ±0       0 ❌ ±0 

Results for commit 5a05cb8. ± Comparison against base commit a06f23e.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

Integration Test Results

 60 files  ±0   60 suites  ±0   45m 11s ⏱️ + 2m 25s
428 tests ±0  418 ✅ ±0  10 💤 ±0  0 ❌ ±0 
431 runs  ±0  421 ✅ ±0  10 💤 ±0  0 ❌ ±0 

Results for commit 5a05cb8. ± Comparison against base commit a06f23e.