includeThreadDumpInDeadlockExceptions always includes the thread dump, even when it is not a deadlock exception

When the option includeThreadDumpInDeadlockExceptions is set to true, any SQL exception causes a thread dump to be added to the exception message.

org.mariadb.jdbc.internal.util.exceptions.ExceptionFactory.buildMsgText(String, long, Options, Exception) does this:

if (options != null

        && options.includeInnodbStatusInDeadlockExceptions

        && deadLockException != null) {

      msg.append("\ndeadlock information: ").append(deadLockException);

}

if (options != null && options.includeThreadDumpInDeadlockExceptions) {

  // append thread dump

}

I'm not confident with this code, but I suspect that the second block should also be executed only if deadLockException != null.