Extend PgConnectionSupplier so we can also use it for releasing connections

[joshiste]

Expected Behavior

Also use PgConnectionSupplier to release connections;

Current Behavior

PgConnectionSupplier is only used to obtain a connection.

Context

You may need to know when the connection is returned (e.g., for o11y or AWS IAM auth).
So also having an optional release method on this would make life easier (without subclassing PGConnection)

[artembilan]

We introduced PgConnectionSupplier just for easier way to distinguish from the standard java.util.function.Supplier.
Plus re-throw that checked SQLException.

So, don't look at this a first-class API for end-users.

That is really not this PgConnectionSupplier contract responsibility to manage target object lifecycle.
It is deliberately supplier, so target application may chose any way to manage and provide low-level connection object.
What you are asking is out of this project scope and that connection lifecycle has to be managed exactly in your application.
You may delegate from this PgConnectionSupplier to another supplier or so where you would do that release or close.

BTW, the PostgresChannelMessageTableSubscriber properly closes supplied connection when it is not needed any more.