[ci-scan] Test failure: GC/API/GC/Collect_Aggressive_LargePages on NativeAOT windows-x64

## Build Information

Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1521210
Pipeline: runtime-nativeaot-outerloop (definition 265), branch `main`
Failing leg: `NativeAOT_Pri1` on `windows-x64`
Failing test: `GC/API/GC/Collect_Aggressive_LargePages/Collect_Aggressive_LargePages.cmd`

## Error Message

The test exits with a crash (`Actual: -1`) instead of the expected pass code under the NativeAOT windows-x64 outer-loop leg:

```
Running test: GC\API\GC\Collect_Aggressive_LargePages\Collect_Aggressive_LargePages.cmd
Expected: 100
Actual: -1
END EXECUTION - FAILED
Failed test: GC\API\GC\Collect_Aggressive_LargePages\Collect_Aggressive_LargePages.cmd
```

```json
{
"ErrorMessage": "Failed test: GC\\API\\GC\\Collect_Aggressive_LargePages\\Collect_Aggressive_LargePages.cmd",
"BuildRetry": false,
"ExcludeConsoleLog": false
}
```

## Occurrences

Stable across the scanned window: source build 1521210, follow-up build 1522302, and prior build 1520338 all reproduce this signature on the NativeAOT `windows-x64` leg.

First build it occurred: 1520338 (oldest build in scanned window still showing this signature; true origin may predate it).

Related: dotnet/runtime#130211, dotnet/runtime#130302, dotnet/runtime#130432 — same test `Collect_Aggressive_LargePages`, but distinct signatures (linux SIGSEGV exit 139, linux OOM `0x8007000E` exit 255, and a CoreCLR `GCCoop` regex respectively). This KBE covers the NativeAOT windows-x64 `Actual: -1` crash manifestation, which none of those match.

---

Filed by [`ci-failure-scan`](https://github.com/dotnet/runtime/blob/main/.github/workflows/ci-failure-scan.md); mitigation is tracked by [`ci-failure-fix`](https://github.com/dotnet/runtime/blob/main/.github/workflows/ci-failure-fix.md).

> [!NOTE]
> This issue was generated by an AI agent (GitHub Copilot). Please review for accuracy.

> [!WARNING]
>
> Firewall blocked 1 domain
>
> The following domain was blocked by the firewall during workflow execution:
>
> - `awmgmcpg`
>> To allow these domains, add them to the `network.allowed` list in your workflow frontmatter:
>
> ```yaml
> network:
> allowed:
> - defaults
> - "awmgmcpg"
> ```
>
> See [Network Configuration](https://github.github.com/gh-aw/reference/network/) for more information.
>
>

> Generated by [CI Outer-Loop Failure Scanner](https://github.com/dotnet/runtime/actions/runs/30009425821) · 992.5 AIC · ⌖ 15.3 AIC · ⊞ 18.6K · [◷](https://github.com/search?q=repo%3Adotnet%2Fruntime+is%3Aissue+%22gh-aw-workflow-call-id%3A+dotnet%2Fruntime%2Fci-failure-scan%22&type=issues)

### Report
#### Summary
|24-Hour Hit Count|7-Day Hit Count|1-Month Count|
|---|---|---|
|0|0|0|

Start with the NativeAOT_Pri1 windows-x64 build results and the failing test at GC/API/GC/Collect_Aggressive_LargePages/Collect_Aggressive_LargePages.cmd. Compare builds 1521210, 1522302, and 1520338, and review the related issues for differing signatures; done means this test exits with the expected pass code on the NativeAOT windows-x64 leg.

Written by the indexing model from the issue text.