Add native AOT compile verification

[anuchandy]

What does this PR do?

[Provide a clear, concise description of the changes]

Add Native AOT build verification to CI to catch compatibility issues on PRs.

[Any additional context, screenshots, or information that helps reviewers]

GitHub issue number?

[Link to the GitHub issue this PR addresses]

Pre-merge Checklist

• Required for All PRs
  • Read contribution guidelines
  • PR title clearly describes the change
  • Commit history is clean with descriptive messages (cleanup guide)
  • Added comprehensive tests for new/modified functionality
  • Updated CHANGELOG.md for product changes (features, bug fixes, UI/UX, updated dependencies)
  • Spelling check passes: .\eng\common\spelling\Invoke-Cspell.ps1
• For MCP tool changes:
  • Updated README.md documentation
  • Updated command list in /docs/azmcp-commands.md
  • Updated test prompts in /e2eTests/e2eTestPrompts.md
  • For new or modified tool descriptions, ran the eng/tools/ToolDescriptionConfidenceScore tool and obtained a result >= 0.4
• 👉 For Community (non-Azure team member) PRs:
  • Security review: Reviewed code for security vulnerabilities, malicious code, or suspicious activities before running tests (crypto mining, spam, data exfiltration, etc.)
  • Manual tests run: added comment /azp run azure - mcp to run Live Test Pipeline

[vcolin7]

LGTM, but maybe we should get @hallipr or @weshaggard to take a look before merging.

[weshaggard]

What is different between this and "Run AOT Compatibility Analysis"? Aren't they both trying to do this analysis?

[anuchandy]

What is different between this and "Run AOT Compatibility Analysis"? Aren't they both trying to do this analysis?

@weshaggard, the main difference is -

1. The AOT analysis step does not produce the native binary but run analyzer. This analyzer runs on the "entire code base" and report warnings, without blocking any pr.
2. The AOT build step runs analyzer and attempt to build the native binary. The build step runs on "subset of code base", which authors marked as AOT safe (via BUILD_NATIVE block and conditional), and make sure it’s really AOT safe else block the pr.

So, while 1 let’s know the entire state of the repro without failing but as warnings, the 2 ensure the areas marked to ship as AOT is really safe or fail the pr otherwise.

The plan is to ship the "native binary" (for the subset of AOT safe areas) side-by-side with the .NET-based one for dogfooding. Once the entire repo is AOT-safe, we'll ship only the native binary (as mentioned in Josh’s email last Friday). This PR is the first step toward that goal.

[Copilot]

Pull Request Overview

This PR adds Native AOT (Ahead-of-Time) compilation verification to the CI pipeline to catch compatibility issues early. The verification runs on Linux x64 during PR builds to ensure the codebase remains AOT-compatible.

• Adds a new build step in the CI pipeline that performs Native AOT compilation
• Modifies the build script to support Native AOT builds and clean up artifacts
• Includes build artifact cleanup to ensure clean builds

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
eng/scripts/Build-Module.ps1	Refactors project path variables and adds cleanup of build artifacts
eng/pipelines/templates/jobs/build.yml	Adds new Native AOT build verification step to the CI pipeline