[Repo Assist] fix: widen vswhere version range to detect VS 2019 and VS 2022 in DacPacReport

[github-actions]

🤖 This PR was created by Repo Assist, an automated AI assistant.

Summary

Fixes automatic SqlPackage.exe detection in the DacPacReport task when Visual Studio 2019 or VS 2022 is installed, as reported in #193.

Root Cause

FindSqlPackagePath.ps1 contains the function Get-VisualStudio_15_0 which calls vswhere.exe with -version [15.0,16.0). This range only matches Visual Studio 2017 (which is version 15.x):

• VS 2017 → version 15.x ✅ (previously found)
• VS 2019 → version 16.x ❌ (missed)
• VS 2022 → version 17.x ❌ (missed)

After the VS 15.x check fails, the code falls back to a registry-based scan that only covers VS 2013 and 2015. Machines with only VS 2019+ installed fell through all detection paths.

Fix

Changed the vswhere -version argument from [15.0,16.0) to [15.0,] (no upper bound), applied to both the standard and BuildTools product queries:

# Before — only VS 2017
-version [15.0,16.0) -latest -format json

# After — VS 2017, 2019, 2022 and beyond
-version [15.0,] -latest -format json

The -latest flag ensures the highest installed version is selected.

Trade-offs

• Minimal, surgical change (2 lines)
• Fully backward-compatible — existing VS 2017 environments are unaffected
• No behavioral change when userSqlPackagePath is set explicitly

Test Status

⚠️ Infrastructure: Full test execution is not available in this CI environment (no node_modules). The change is a PowerShell string argument modification and was verified by code inspection. The logic change is straightforward.

Closes #193

Generated by Repo Assist