[ci-scan] Android LayoutShouldBeCorrectOnFirstNavigation snapshot differs from baseline

## Summary
The Android `LayoutShouldBeCorrectOnFirstNavigation` visual test repeatedly differs from its baseline on main.

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

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

## Error Message
```
2026-08-15T22:13:09.7752048Z Snapshot different than baseline: LayoutShouldBeCorrectOnFirstNavigation.png (1.78% difference)
```

## Recommended Action
Inspect `Issue33038.LayoutShouldBeCorrectOnFirstNavigation` and its Android baseline. Determine whether the rendering change is expected; update the baseline only if the current layout is correct, otherwise fix the Android first-navigation layout.

Inspect the Issue33038.LayoutShouldBeCorrectOnFirstNavigation visual test and its Android baseline, using the linked maui-pr-uitests build and the reported 1.78% snapshot difference as the starting evidence. Compare the current rendering with the baseline to determine whether the change is expected; done means either an appropriate baseline update or a fix for the Android first-navigation layout.

Written by the indexing model from the issue text.