V2.13.0 <- V2.12.3

[jworkmanjc]

Issues

Merge v2.12.3 into v.2.13.0 for release

What does this solve?

Is there anything particularly tricky?

How should this be tested?

Screenshots

---

Note

Medium Risk
Moderate risk: changes touch migration execution paths (exe acquisition/validation, domain unjoin via CIM, and system description reads/writes) and JumpCloud API region selection, which could impact remote migrations if misconfigured or if validation logic is too strict.

Overview
Adds a new localEXEs mode across Start-Migration and the JumpCloud Agent invoke script to allow using pre-staged gui_jcadmu.exe/uwp_jcadmu.exe locally, with GitHub SHA/version validation when available and explicit pre-flight checks/fallback behavior when the GitHub API is rate limited.

Expands multi-region support by adding the IN console endpoint and updating multiple JumpCloud API call sites (org lookup, username search, system-context region detection, device init scripts) to try US/EU/IN endpoints.

Introduces new bulk device-description utilities (Get-DeviceDescriptionToCSV.ps1, Set-DeviceDescriptionFromCSV.ps1) to export user objects embedded in device descriptions to CSV and selectively sync edited CSV changes back to device descriptions with validation/preview.

Also includes CI/test and code-quality updates: adds PSScriptAnalyzer + Pester dependencies, increases Pester verbosity, adds new acceptance/unit tests for the new UWP exe helpers and description tooling, and refactors several WMI calls to CIM/Invoke-CimMethod plus minor PSScriptAnalyzer compliance tweaks.

^{Reviewed by Cursor Bugbot for commit d4cdaab. Bugbot is set up for automated code reviews on this repo. Configure here.}