PLSQLJob should close remaining sessions on termination

Current Situation

• The PLSQLJob does not close sessions when terminating. This can exhaust available connections to the DBMS.
• If the job is configured for use of credentials from arguments instead of a Hibernate configuration file, then the Hibernate default connection pool (hibernate implementation) is used and is instantiated with potentially 20 open connections.
• The previous implementation of the job did commit open transactions due to a fallback in the Oracle® JDBC Driver.

Desired Behavior

• The PLSQLJob should close remaining sessions when terminating. This applies to normal job termination and in the event of cancel/kill or suspend/kill operations. The job should roll back open transactions before terminating to prevent a situation when a user's SQL code opens a transaction that is not committed and not rolled back.
• The PLSQLJob should use the Hikari Connection Pool by default. Users who apply a Hibernate configuration file can specify a different connection pool product.
• The connection pool should be instantiated with a maximum pool size of 1 as the job makes use of a single connection to the database.

Patch

• 2.7.0
  • https://download.sos-berlin.com/patches/2.7.0-patch/js7_agent.2.7.0-PATCH1.JITL-743.jar [sha256] [sig] [tsr]
• 2.7.1
  • https://download.sos-berlin.com/patches/2.7.1-patch/js7_agent.2.7.1-PATCH1.JITL-743.jar [sha256] [sig] [tsr]