[EPIC] Fix database connection leak

[tuliren]

Summary

Some of the JdbcDatabase methods return a stream embedded with a database connection. The connection can only be closed when the consumption of the stream is done (in an onClose callback), and the closure is not automatic. There are use cases that do not manually close those streams. This is not an intuitive operation because most Java streams do not require closure, as they are not involved with resources.

Tasks

• Ensure every JDBC database use case that returns a stream is closed #10129
• Try Sentry JDBC profiling to monitor production connection usage
• Make sure we close the connection and don't leak it in java sources. #10128