Bumps [fast-uri](https://github.com/fastify/fast-uri) from 3.1.1 to 3.1.2.
- [Release notes](https://github.com/fastify/fast-uri/releases)
- [Commits](fastify/fast-uri@v3.1.1...v3.1.2)

---
updated-dependencies:
- dependency-name: fast-uri
  dependency-version: 3.1.2
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>

…uri-3.1.2

chore(deps-dev): bump fast-uri from 3.1.1 to 3.1.2

Non-standard boolean options (useUTC, stream, parseJSON) were not part
of the MSSQL_SCHEMA, so they were passed through as raw strings by
the connection string parser. This caused values like "False" to be
coerced to true via the `!!` operator (since any non-empty string is
truthy).

Extend the MSSQL_SCHEMA with these node-mssql-specific keys so that
toSchema() handles the string-to-boolean conversion. Also add
request timeout as a number type.

Closes #1860

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

…rsing

fix: parse boolean connection string options correctly

When a transaction is aborted (e.g. by XACT_ABORT or deadlock), subsequent
commit() or rollback() calls return a TransactionError with code EABORT.
Previously, originalError was always undefined on these errors because the
error was constructed with a string message rather than an Error object.

Now the actual request error that triggered the abort is captured and
attached as originalError on the EABORT TransactionError. A generic
fallback is used when the specific error cannot be captured (e.g.
connection-level errors).

Closes #1716

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

fix: preserve originalError on EABORT TransactionError