Bump unboundid-ldapsdk from 6.0.5 to 6.0.6

[dependabot]

Bumps unboundid-ldapsdk from 6.0.5 to 6.0.6.

Changelog

Sourced from unboundid-ldapsdk's changelog.

          <div align="right">

${TARGET="offline"} LDAP SDK Home Page ${TARGET="offline"} Product Information

          <h2>Release Notes</h2>
      &lt;h3&gt;Version 6.0.6&lt;/h3&gt;
  &amp;lt;p&amp;gt;
    The following changes were made between the 6.0.5 and 6.0.6 releases:
  &amp;lt;/p&amp;gt;

  &amp;lt;ul&amp;gt;
    &amp;lt;li&amp;gt;
      Fixed an issue that could cause request failures when closing a connection that
      has outstanding operations in the default asynchronous mode, immediately
      re-establishing the connection (to the same or a different server), and sending
      a request on the newly established connection.  However, we generally recommend
      creating a new connection object (or using a connection pool) in these cases,
      rather than closing and re-establishing the same connection object.
      &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;
    &amp;lt;/li&amp;gt;

    &amp;lt;li&amp;gt;
      Fixed an issue that could interfere with the ability to get a default SSLContext
      on modern versions of Java (e.g., Java 17) when using the LDAP SDK in FIPS
      140-2-compliant mode.
      &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;
    &amp;lt;/li&amp;gt;

    &amp;lt;li&amp;gt;
      Updated the LDAPConnectionOptions class to add support for a new
      com.unboundid.ldap.sdk.LDAPConnectionOptions.defaultVerifyCertificateHostnames
      system property that can be used to enable certificate hostname verification by
      default.  This verification was previously available by calling the
      LDAPConnectionOptions.setSSLSocketVerifier method with a
      HostNameSSLSocketVerifier instance, but the new system property can be used to
      enable this verification by default without any code changes.  Even though
      hostname verification is strongly recommended, it is disabled by default in the
      LDAP SDK for backward compatibility purposes, and for compatibility with a wide
      range of development, test, and even production environments that are not
      properly set up with certificates that allow for hostname verification.
      &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;
    &amp;lt;/li&amp;gt;

    &amp;lt;li&amp;gt;
      Updated the LDAP command-line tool framework to add a new
      &amp;quot;--verifyCertificateHostnames&amp;quot; argument that can be used to enable hostname

... (truncated)

Commits

• See full diff in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[quarkus-bot]

/cc @Karm, @jerboaa

[quarkus-bot]

Failing Jobs - Building 566f16d

Status	Name	Step	Failures	Logs	Raw logs
✔️	JVM Tests - JDK 11
⌛	JVM Tests - JDK 11 Windows	Upload gc.log	⚠️ Check →	Logs	Raw logs
✔️	JVM Tests - JDK 17
✔️	JVM Tests - JDK 18