Update PostgreSQL connection pool handling

[mpastecki]

Description

This improves the handling of database pool connections that are explicitly used in the code to verify SSL settings and to set up the database schema-change listener. Previously, these two clients were either idle or waiting for the rare event of a schema change.

In environments where idle TCP connections are eventually killed, these connections were terminated, causing the entire app to crash due to an uncaught exception.

Additionally, an error handler has been attached to the schema change PostgreSQL client to listen for error events. This should improve visibility into any issues that arise. When an error occurs, it will be logged, and the application will be terminated to prevent potential data corruption.

Fixes (#2520 )

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Checklist

• I have tested locally
• I have performed a self review of my changes
• Updated any relevant documentation
• Linked to any relevant issues
• I have added tests relevant to my changes
• Any dependent changes have been merged and published in downstream modules
• My code is up to date with the base branch
• I have updated relevant changelogs. We suggest using chan

[stwiname]

This looks good, just a couple of minor improvements

[mpastecki]

Thanks, updated.