fix: add connection timeout for db conn pool

[cch123]

Purpose or design rationale of this PR

Database conn pool should specify strategy for conn timeout

1. for idle connections, should shrink the pool to save more resources
2. for connections, if network partition or LB switch happened, the original conns will die, but app will not know this until the code runs to reading/writing on this conn. There should be a way to evict the expired conn. if there is a dbproxy between app and mysql, this max lifetime should be less than the proxy config.

These two params should also considered under your db architecture~

Deployment tag versioning

Has tag in common/version.go been updated or have you added bump-version label to this PR?

• No, this PR doesn't involve a new deployment, git tag, docker image tag
• Yes

Breaking change label

Does this PR have the breaking-change label?

• No, this PR is not a breaking change
• Yes

[codecov]

Codecov Report

Attention: 2 lines in your changes are missing coverage. Please review.

Comparison is base (bc5ec89) 48.03% compared to head (3dcea12) 48.04%.

Files	Patch %	Lines
bridge-history-api/utils/database.go	0.00%	2 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff            @@
##           develop    #1032   +/-   ##
========================================
  Coverage    48.03%   48.04%           
========================================
  Files          101      101           
  Lines        10692    10697    +5     
========================================
+ Hits          5136     5139    +3     
- Misses        5126     5128    +2     
  Partials       430      430           

Flag	Coverage Δ
bridge-history-api	11.11% <0.00%> (-0.02%)	⬇️
common	55.05% <100.00%> (+0.11%)	⬆️
coordinator	18.91% <ø> (ø)
database	42.85% <ø> (ø)
rollup	66.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.