feat(ir): add typed builder for VSBuild@1

[github-actions]

Summary

Adds a typed builder struct for VSBuild@1 to the ado-aw IR.

Motivation

Previously, any code that needed to emit a VSBuild@1 step had to hand-craft
TaskStep::new("VSBuild@1", ...) with raw string input keys. This PR introduces
a typed builder struct (new(solution) + typed optional setters + into_step())
so the required input is positional, optional inputs and their constrained values
are type-checked, and call sites stop using stringly-typed keys.

Changes

• src/compile/ir/tasks/vs_build.rs: new VsBuild builder struct with typed enums
  (VsVersion, MsBuildArchitecture, LogFileVerbosity) and #[cfg(test)] mod tests
• src/compile/ir/tasks/mod.rs: pub mod vs_build; declaration (alphabetical order)

ADO Task Reference

• Task: VSBuild@1
• Docs: https://learn.microsoft.com/en-us/azure/devops/pipelines/tasks/reference/vsbuild-v1-task
• Required inputs: solution (glob pattern, e.g. **\*.sln)
• Optional inputs:
  • vsVersion — typed enum VsVersion (Latest, Vs2022, Vs2019, Vs2017, Vs2015, Vs2013)
  • msbuildArgs — additional MSBuild arguments
  • platform — target platform (x86, x64, Any CPU)
  • configuration — build configuration (Debug, Release)
  • clean — clean build (bool)
  • maximumCpuCount — use all CPUs (bool)
  • restoreNugetPackages — restore NuGet before build (bool)
  • msbuildArchitecture — typed enum MsBuildArchitecture (X86, X64, Arm64)
  • logProjectEvents — log project-level events (bool)
  • createLogFile — write build log file (bool)
  • logFileVerbosity — typed enum LogFileVerbosity (Quiet, Minimal, Normal, Detailed, Diagnostic)
  • enableDefaultLogger — enable default logger (bool)
  • customVersion — custom VS version string

Validation

• cargo build --all-targets
• cargo test (2263+ tests passing, 0 failed)
• cargo clippy --all-targets --all-features --workspace -- -D warnings

---

Created by the ado-task-ir-contributor workflow.

Warning

Firewall blocked 2 domains

The following domains were blocked by the firewall during workflow execution:

• spsprodeus21.vssps.visualstudio.com
• spsprodweu4.vssps.visualstudio.com

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "spsprodeus21.vssps.visualstudio.com"
    - "spsprodweu4.vssps.visualstudio.com"

See Network Configuration for more information.

Generated by ADO Task IR Contributor · 1K AIC · ⌖ 44.1 AIC · ⊞ 38.7K · ◷