Replace logging with usages of java.lang.System.Logger

[mrotteveel]

Consider replacing logging with usages of java.lang.System.Logger.

Benefits:

• No more custom logging interface in Jaybird itself
• java.lang.System.Logger defaults to java.util.logging if present, and - if the java.logging module is not loaded - gracefully degrades to printing to System.err
• java.lang.System.Logger is pluggable, so another logging framework can be used

Downsides

• If users use a custom implementation of org.firebirdsql.logging.Logger, they'll need to switch to implementing System.LoggerFinder and System.Logger
• Some of the more esoteric logging options added in the current logger will be unavailable (like warnDebug and errorDebug to log a message on warn/error and the full stacktrace on debug); though we can address that with static helpers, or just live without
• Current options to control/disable logging (e.g. org.firebirdsql.jdbc.forceConsoleLogger, org.firebirdsql.jdbc.disableLogging and org.firebirdsql.jdbc.loggerImplementation will no longer be avilable

[mrotteveel]

NOTE: This is tentatively scheduled for Jaybird 6, but this may move to a later version or be scrapped entirely.

[mrotteveel]

NOTE: Dependency on module java.logging does not go away, as the JDBC API declares methods returning a java.util.logging.Logger in java.sql.Driver and javax.sql.DataSource.