Reorder regression steps after HW smoke tests

[hoffmang9]

Summary

• Move GoogleTest regression execution to run immediately after HW smoke checks on non-Windows jobs.
• Move Windows GoogleTest regressions to run immediately after Windows HW smoke checks.
• Rename the non-Windows regression step label to Ubuntu/macOS to match actual coverage.

Test plan

• Run the build-packages workflow on this branch.
• Confirm optimized Ubuntu/macOS/Windows jobs execute HW smoke before GoogleTest regressions.
• Confirm regressions still run only for optimized=1 matrix entries.

Made with Cursor

---

Note

Low Risk
Workflow-only reordering/label change; no production code changes, with minimal risk aside from possible CI ordering assumptions.

Overview
Reorders build-packages.yml test execution so GoogleTest regression suites run immediately after the HW smoke checks on both Unix (renamed to Ubuntu/macOS) and Windows optimized jobs.

No test selection/filters change beyond step placement; regressions still run only for optimized=1 matrix entries.

^{Written by Cursor Bugbot for commit 540134f. This will update automatically on new commits. Configure here.}