Expose the NT_TARGET_VERSION in the build samples script & workflow update

[5an7y-Microsoft]

Summary

Driver samples in this repo are Universal / Windows‑Driver‑platform drivers (Windows 10+), so the Target OS Version can't be lowered to build "downlevel". The axis that is meaningful is _NT_TARGET_VERSION — the version of the WDK libraries a driver links against. This PR exposes that axis, lets it be exercised across the build matrix, records the samples that can't link against older libraries, and makes both the version list and the CI matrix auto‑discovered (no hand‑maintained version list anywhere).

What changed

• Build-Samples.ps1 — new -NtTargetVersion parameter (also WDS_NtTargetVersion). Accepts 10.0.<build> or the short <build> tag; defaults to the latest. Valid values, and their NTDDI codes, are resolved at build time (no hard‑coded list). Also emits an easy‑to‑scan GitHub job summary ($GITHUB_STEP_SUMMARY).
• Get-NtTargetVersions.ps1 (new) — auto‑discovers the valid _NT_TARGET_VERSION values by parsing the active WDK's DriverGeneral.xml rule (from the restored NuGet package or the installed WDK). A new WDK version is picked up automatically.
• exclusions.csv — new optional MinNtTargetVersion / MaxNtTargetVersion columns (inclusive range; blank = unbounded) plus per‑sample exclusions for the samples that only fail when linking against older library sets (see table below). Old/short CSVs without these columns keep working (missing column = "all versions").
• CI (ci.yml, ci-pr.yml) — a discover job emits the newest‑N versions as JSON; the build matrix consumes it via fromJSON, so each version × configuration × platform runs on its own parallel runner with no version list maintained in YAML. The report job (Join-CsvReports.ps1) writes a consolidated, version‑aware summary to the run page. Build-ChangedSamples.ps1 treats the discovery script as a full‑build trigger.
• Building-Locally.md — documents the new parameter, auto‑discovery, and the exclusions format.

exclusions.csv — what's excluded and why

Each row below only applies when linking against an older library set (i.e. _NT_TARGET_VERSION at or below the listed threshold); on the latest version these samples build normally. Reasons are recorded verbatim in the Reason column of exclusions.csv.

Sample	Scope	Excluded when	Why (compiler error)
audio\sysvad	all configs/platforms	_NT_TARGET_VERSION ≤ 10.0.22000	KSJACK_DESCRIPTION3 undeclared — the audio jack descriptor v3 struct was added in 22H2 (10.0.22621).
network\netadaptercx\netvadapter	all configs/platforms	≤ 10.0.22621	Requests an NDIS/DDI version newer than the linked library (C1189 "wrong NDIS or DDI version").
network\wlan\wificx	all configs/platforms	≤ 10.0.22621	Requests an NDIS/DDI version newer than the linked library (C1189 "wrong NDIS or DDI version").
powerlimit\plclient	all configs/platforms	≤ 10.0.22621	POWER_LIMIT_ATTRIBUTES not declared in the older library (C2061).
powerlimit\plpolicy	all configs/platforms	≤ 10.0.22621	POWER_LIMIT_ATTRIBUTES not declared in the older library (C2061).
storage\class\classpnp	Debug only (both platforms)	≤ 10.0.22621	STOR_ADDRESS_TYPE_NVME undeclared in the older library (C2065).
storage\miniports\storahci	Debug only (both platforms)	≤ 10.0.22621	STOR_ADDRESS_TYPE_NVME undeclared in the older library (C2065).
storage\msdsm	Debug, x64 only	≤ 10.0.22621	STOR_ADDRESS_TYPE_NVME undeclared in the older library (C2065).

Note: usb\usbview is intentionally not excluded. It fails for a host‑tooling reason (missing .NET Framework 4.7.2 / 4.8.1 targeting packs) on every version, not because of _NT_TARGET_VERSION.

Testing

• Builds the full matrix; the samples above are reported as Excluded (skipped, not failed) on the versions where they can't link, and build normally on the latest.
• _NT_TARGET_VERSION auto‑discovery, default‑to‑latest, validation of bad values, and the report/summary output were all verified locally.
• Pipeline run on my fork: https://github.com/5an7y-Microsoft/Windows-driver-samples-2/actions/runs/28051190470