expose Lifetime in HikariConfig

We run into an issue with HikariCP on Postgres with PgBouncer, that the connection in local pool is expired already, temporally we move to none_cp mode to mitigate the issue. By exposing maxLifetime in HikariConfig, we would be able to fix it.

Regarding to the issue:

• PgBouncer has one conf server_lifetime, named as T0, to expire long idle connections;

•  HikariCP has maxLifetime with default as 1800_s, named as T1;

When T1 > T0, HMS connection_pool would hold connections which is expired by pgbouncer already. For operation reasons, we prefer to keep a short conn_lifetime instead of increasing T0.