fix: prioritize EWDK over NuGet in auto-detection

The packages\ folder is a passive disk artifact that persists between
builds. If someone runs the script from inside an EWDK command prompt
while packages\ exists from a previous NuGet restore, Auto mode would
incorrectly select NuGet and then fail trying to find a VS installation
that may not be present in an EWDK-only setup.

EWDK is now checked first because \ being set is an active,
explicit signal that the user is intentionally in the EWDK environment.

Auto detection order is now: EWDK -> NuGet -> WDK

Co-authored-by: Copilot <[email protected]>

0 files changed, 0 insertions, 0 deletions