This is a backport of the PR #169 to `v1.3-ossivalis` stable branch.

This change adds `_DISABLE_CONSTEXPR_MUTEX_CONSTRUCTOR` flag for Windows
builds that prevents crashes when the host process, into which the
ODBC driver is loaded, is run using older versions of C++ stdlib.

Details: duckdb/duckdb#17991

Testing: additional test run added that uses `msvcp140.dll` from VS2019
instead of the system-provided one.

This is a backport of the PR #172 to `v1.3-ossivalis` stable branch.

  - Handle sign field (0=negative, 1=positive) when binding SQL_NUMERIC_STRUCT parameters
  - Fix SQLGetData conversion of large decimals by using TryCast instead of TryCastToDecimal
  - Add exception handling for std::stoi to prevent overflow with large decimal fractions
  - Add tests for negative decimals in both parameter binding and result retrieval

This is a backport of the PR #175 to `v1.3-ossivalis` stable branch.

This change increases the max column size for `VARCHAR` and `VARBINARY`
fields reported in `SQLDescribeCol` (or `SQLColAttribute`) call.

Per ODBC spec this value is defined as:

> The defined or maximum column size in characters of the column

In DuckDB `VARCHAR` fields don't have the upper limit. We would like to
return `std::numeric_limits<SQLINTEGER>::max()` as max size, but it
appeared that `MSDASQL` provider cannot read strings when the declared
column size is over `8000`, that is the max size of a `VARCHAR`
(excluding `VARCHAR(MAX)`) in MSSQL.

Testing: tested manually with local MSSQL; automated tests are
problematic as `OPENROWSET` calls in MSSQL are disabled by default under
`Ad Hoc Distributed Queries` permission.

Fixes: #168

This is a backport of the PR #176 to `v1.3-ossivalis` stable branch.

This is a backport of the PR #177 to `v1.3-ossivalis` stable branch.

This change addresses multiple ODBC specification conformance issues discovered
during a thorough audit of GetColumnSize() and GetDisplaySize() implementations.

Issues fixed:
1. DECIMAL/NUMERIC precision and scale reporting
    - SQLColAttribute/SQLDescribeCol incorrectly reported column sizes
    - Fixed GetColumnSize() to return precision instead of precision+scale

2. Signed/Unsigned integer display sizes
    - GetDisplaySize() now correctly distinguishes signed vs unsigned types
    - UTINYINT: 3 chars, USMALLINT: 5 chars, UINTEGER: 10 chars, UBIGINT: 20 chars
    - TINYINT: 4 chars, SMALLINT: 6 chars, INTEGER: 11 chars, BIGINT: 20 chars

3. TIME/TIMESTAMP fractional seconds precision
    - Added GetTemporalPrecision() to detect precision from LogicalTypeId
    - Added missing type mappings for TIMESTAMP_MS, TIMESTAMP_SEC, TIMESTAMP_NS
    - Fixed GetColumnSize() to return full column size per ODBC spec:
    * TIME: 8 (base) or 9 + precision
    * TIMESTAMP: 19 (base) or 20 + precision
    - Fixed GetDisplaySize() to include fractional seconds in display size
    - Updated FillIRD() and SQLDescribeCol to set precision/scale for temporal types

Implementation details:
- include/api_info.hpp: Added GetTemporalPrecision(), updated size calculations
- src/api_info.cpp: Added missing timestamp variant type mappings
- src/common/duckdb_odbc.cpp: Set temporal precision/scale in IRD
- src/prepared.cpp: Handle temporal types in SQLDescribeCol
- test/: Added comprehensive test coverage for all fixes

All changes verified against DuckDB behavior and ODBC specification.
All 79 tests passing with new test coverage added.