Extend database pool options

[rmn-boiko]

Description

Checklist before requesting a review

• Unit and integration tests added
• Compatibility:
  • Network APIs: ✅
  • Workspace layout and metadata: ✅
  • Configuration: ✅
  • Container images: ✅
• Observability:
  • Tracing / metrics: ✅
  • Alerts: ✅
• Documentation:
  • Changelog: ✅
  • Public documentation: ✅
• Downstream effects:
  • kamu-node: ✅
  • kamu-web-ui: ✅
  • release-queue

[sergiimk]

LGTM, but consider modifying the PR description not to close the linked ticket until these options are also exposed in api-server's config

[zaychenko-sergei]

1. I think it can be supported by MySQL easily, for consistency.
2. For SQLite, think of some configuration error mechanism or a warning that these settings are ignored.

[rmn-boiko]

2. For SQLite, think of some configuration error mechanism or a warning that these settings are ignored.

Such as these configurations are optional do we really need to add warnings for Sqlite if they are not presented?