SOS.Tests VerifyHeap_ReportsNoCorruption rejects output without “0 errors”

## Build Information
Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1578741
Leg Name: Windows_Test_x64_Debug
Build error leg or test failing: SOS.Tests.GcInspectionTests.VerifyHeap_ReportsNoCorruption

## Error Message

```json
{
"ErrorPattern": [
"Assert\\.Matches\\(\\) Failure: Pattern not found in value",
"Regex: .+0 errors.+",
"Value: .+Segment +Object +Failure"
],
"BuildRetry": false,
"ExcludeConsoleLog": false
}
```

`VerifyHeap_ReportsNoCorruption` requires the exact phrase `0 errors`. In two Windows x64 Debug matrix cases, `verifyheap` returned its segment/object/failure table without that phrase, causing the assertion to fail.

Investigate whether this is a valid host/runtime/DAC output variation or an SOS regression. If valid, the test should assert semantically that no corruption records were reported while retaining `No heap corruption detected`. Until resolved, skip only the confirmed configurations and link the skip to this issue.

### Known issue validation
**Build: :mag_right:** https://dev.azure.com/dnceng-public/public/_build/results?buildId=1578741
**Error message validated:** `[Assert\.Matches\(\) Failure: Pattern not found in value Regex: .+0 errors.+ Value: .+Segment +Object +Failure`]
**Result validation:** :x: Known issue did not match with the provided build.
**Validation performed at:** 9/2/2026 9:57:00 PM UTC

### Report

|Build|Repository|Test|Pull Request|
|---|---|---|---|
|[1593730](https://dev.azure.com/dnceng-public/public/_build/results?buildId=1593730)|dotnet/diagnostics|[SOS.Tests.ClrThreadsTests.SOS.Tests.ClrThreadsTests.ClrThreads_ReportsThreadCount](https://dev.azure.com/dnceng-public/public/_build/results?buildId=1593730&view=ms.vss-test-web.build-test-results-tab&runId=43989976&resultId=100000)|dotnet/diagnostics#6019|
|[1593469](https://dev.azure.com/dnceng-public/public/_build/results?buildId=1593469)|dotnet/diagnostics|[SOS.Tests.GcInspectionTests.SOS.Tests.GcInspectionTests.VerifyHeap_ReportsNoCorruption](https://dev.azure.com/dnceng-public/public/_build/results?buildId=1593469&view=ms.vss-test-web.build-test-results-tab&runId=43984760&resultId=100060)|dotnet/diagnostics#6019|
|[1579739](https://dev.azure.com/dnceng-public/public/_build/results?buildId=1579739)|dotnet/diagnostics|[SOS.Tests.GcInspectionTests.VerifyHeap_ReportsNoCorruption](https://dev.azure.com/dnceng-public/public/_build/results?buildId=1579739&view=ms.vss-test-web.build-test-results-tab&runId=43577332&resultId=100384)||
|[1578741](https://dev.azure.com/dnceng-public/public/_build/results?buildId=1578741)|dotnet/diagnostics|[SOS.Tests.GcInspectionTests.VerifyHeap_ReportsNoCorruption](https://dev.azure.com/dnceng-public/public/_build/results?buildId=1578741&view=ms.vss-test-web.build-test-results-tab&runId=43539814&resultId=100374)|dotnet/diagnostics#5979|
#### Summary
|24-Hour Hit Count|7-Day Hit Count|1-Month Count|
|---|---|---|
|0|2|4|

Start with SOS.Tests.GcInspectionTests.VerifyHeap_ReportsNoCorruption and compare the failing Windows x64 Debug build output linked in the issue. Determine whether the segment/object/failure table represents a clean result across the affected configurations, then make the test's assertion match the confirmed output while retaining the stated clean-result wording. Run the affected test configurations to verify the failure is resolved.

Written by the indexing model from the issue text.