[ci-scan-net11] Android SafeArea first-navigation visual baseline differs

## Summary
The Android first-navigation SafeArea visual test repeatedly differs from its checked-in baseline.

## Build Information
- **Pipeline**: maui-pr-uitests
- **Build**: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1554813
- **Build ID**: 1554813
- **Branch**: net11.0
- **First seen**: 2026-08-12
- **Occurrences**: 10 in last 10 builds

## Affected Legs
- Controls SafeAreaEdges / Android API 36 / Pixel 3 XL

## Error Message
```text
2026-08-16T16:43:15.9839713Z Snapshot different than baseline: LayoutShouldBeCorrectOnFirstNavigation.png (6.01% difference)
```

## Recommended Action
Compare the Android actual, baseline, and diff images for `src/Controls/tests/TestCases.Shared.Tests/Tests/Issues/Issue33038.cs`; determine whether first navigation lays out incorrectly or the Android API 36 baseline requires an intentional update.

Start with src/Controls/tests/TestCases.Shared.Tests/Tests/Issues/Issue33038.cs and run the SafeArea first-navigation visual test on Android API 36. Compare the actual, checked-in baseline, and diff images to determine whether the layout is incorrect or the baseline needs an intentional update. Done means the test matches the correct expected behavior and the visual baseline or implementation is updated accordingly.

Written by the indexing model from the issue text.