Fix DatabaseMetaData.getIndexInfo() CachedRowSet invalid cursor position exception

[Ananya2]

Overview
This PR updates DatabaseMetaData.getIndexInfo() to address an issue where calling ResultSet.next() after exhaustion could throw an invalid cursor position exception.
The fix removes the use of CachedRowSet for combining sp_statistics and columnstore index results, and instead uses a UNION ALL query. This ensures standard JDBC cursor behavior while keeping columnstore index support intact.

Problem Description
The current implementation uses CachedRowSet to merge results from sp_statistics and Columnstore index queries. However, CachedRowSet has stricter cursor validation than SQLServerResultSet:

if (cursorPos < 0 || cursorPos >= numRows + 1) {
    throw new SQLException("Invalid cursor position");
}

This causes SQLException: Invalid cursor position when next() is called after the ResultSet has been fully enumerated, which differs from standard JDBC behavior where such calls should simply return false.

Root Cause
Columnstore index support was first added in #2598
to address missing indexes in sp_statistics results. That implementation relied on CachedRowSet to merge sp_statistics output with additional Columnstore index query results, which in turn caused the cursor positioning issue.

Solution

• SQL Server: Replaced CachedRowSet merging with a single UNION ALL query (INDEX_INFO_COMBINED_QUERY) that combines sp_statistics results with Columnstore index data from sys.indexes.
• Azure Synapse DW: Used a dedicated query (INDEX_INFO_QUERY_DW) against sys.indexes to avoid temp table limitations and lack of sp_statistics support.

This eliminates intermediate result set handling and ensures consistent behavior across environments.

Testing

• Validated cursor behavior on both SQL Server and Azure Synapse DW.
• Added comprehensive JUnit tests for ResultSet navigation patterns.
• Verified Columnstore indexes are properly included.
• Confirmed sp_statistics compatibility maintained.

Closes #2758

[codecov]

Codecov Report

❌ Patch coverage is 71.42857% with 4 lines in your changes missing coverage. Please review.
✅ Project coverage is 52.32%. Comparing base (02ee86c) to head (74e9554).

Files with missing lines	Patch %	Lines
...soft/sqlserver/jdbc/SQLServerDatabaseMetaData.java	71.42%	2 Missing and 2 partials ⚠️

Additional details and impacted files

@@            Coverage Diff            @@
##               main    #2763   +/-   ##
=========================================
  Coverage     52.32%   52.32%           
- Complexity     4140     4142    +2     
=========================================
  Files           149      149           
  Lines         34241    34238    -3     
  Branches       5718     5717    -1     
=========================================
+ Hits          17915    17916    +1     
- Misses        13830    13832    +2     
+ Partials       2496     2490    -6     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.