JDBC Lock Acquisition Timeout should behave like the file based version

The journal lock timeout (file-based) is infinite by default, not customizable by the user's configuration and exposed programmatically just for testing purposes: the JDBC version of it need to do the same in order to avoid being misconfigured, breaking JDBC HA reliability.