W-11165796: Update dependency com.microsoft.sqlserver:mssql-jdbc to v11 old renovate pr

[ghost]

This PR contains the following updates:

Package	Type	Update	Change
com.microsoft.sqlserver:mssql-jdbc	test	major	7.0.0.jre8 -> 11.2.1.jre18

---

Configuration

📅 Schedule: Branch creation - "after 8pm every weekday,every weekend,before 8am every weekday" in timezone America/Argentina/Buenos_Aires, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, click this checkbox. ⚠ Warning: custom changes will be lost.

[acurci-at-mulesoft]

Added

• Added support for caching parameter metadata for Always Encrypted with secure enclaves Cache parameter metadata secure microsoft/mssql-jdbc#1866
• Added explicit dependency for com.microsoft.azure.msal4j (was a transitive dependency in previous releases) Update dependencies versions microsoft/mssql-jdbc#1863

Changed

• Changed default loginTimeout value to 30s Updated loginTimeout default value to 30s to be consistent with other drivers microsoft/mssql-jdbc#1885
• Updated dependency versions of com.azure.azure-security-keyvault-keys and com.azure.azure-identity Update dependencies versions microsoft/mssql-jdbc#1863
• Send TDS version 8 in Login7 when in strict mode (encrypt=strict) Send TDS version 8 in Login7 when in strict mode microsoft/mssql-jdbc#1870
• Validate that the serverName field of the connection string does not have an equal sign Parameter order in connection string makes a difference microsoft/mssql-jdbc#1853

Fixed issues

• Fixed intermittent null prepared statement handle error caused by sp_prepare when used with batch queries. Fixed intermittent null prepared statement handle microsoft/mssql-jdbc#1886

• Fixed race condition with addressList which may result in IndexOutOfBoundsException when establishing multiple connections Fixed race condition with addressList microsoft/mssql-jdbc#1855

• Updated secure string usage to prepend Initialization Vector into the encrypted bytes so each IV is unique and preserved with its encrypted bytes for later decryption Fix: Initialization vector cannot be reused microsoft/mssql-jdbc#1858

• Added check for DONE_ERROR status token which may occur from a killed session on the server Added check for DONE_ERROR status token and throw appropriate exception microsoft/mssql-jdbc#1857

• Fixed issue where the driver may assert when canceling a statement Removed assert on attention pending check microsoft/mssql-jdbc#1872

• https://docs.microsoft.com/en-us/sql/connect/jdbc/release-notes-for-the-jdbc-driver?view=sql-server-ver16

• https://github.com/microsoft/mssql-jdbc/releases

• https://github.com/microsoft/mssql-jdbc/blob/main/CHANGELOG.md

[acurci-at-mulesoft]

I changed the version to 11.2.0.jre8

[acurci-at-mulesoft]

BREAKING CHANGE

Encrypt = strict

There is one breaking change in the 11.2 release over previous production releases. To support the new TDS 8.0 protocol where TLS encryption is negotiated before TDS, a new Encrypt option has been added, "strict". This required changing the getEncrypt() API to return a string instead of just a Boolean. Setting Encrypt to "strict" causes the driver to negotiate a TLS connection to the server first, instead of previous behavior where TDS was negotiated, then, if using encryption, TLS would be negotiated inside the TDS stream. Negotiating TLS first means all TDS connection and feature negotiation happens over an encrypted channel.

To read more about TDS 8.0 in SQL Server, see the SQL Server online documentation.

Source: https://techcommunity.microsoft.com/t5/sql-server-blog/jdbc-driver-11-2-for-sql-server-released/ba-p/3595479

[sai-bukka]

Closing this pr as it is generated by old renovate app and marked as ghost